what does the subtreeexpirycleanup.php file do, anyway?

Previous topic

Setup & design

Next topic

Author	Message
Massimiliano Bariola	Wednesday 14 June 2006 9:08:32 am Hi, I never needed to activate the cronjobs until now. So I gave it a few runs from CLI to see if all was ok before trying to cron them. I ran it with php runcronjobs.php -s flc_test_user --logfiles -d --sql I was unable to understand _where_ those logfiles are produced, but it seems that the subtreeexpirycleanup.php script is taking AGES to execute - I am talking about 1.5 hours. Site has about 30000 content objects and makes extensive use of cache-blocks. but as far as I know, cache-blocks are automatically invalidated and regenerated on demand. So my question is .... what's the subtreeexpirycleanup.php file used for? So far, my site has worked well without it, but I am beginning to think I am missing something here. can I safely omit it? and if so, _when should I be using it instead? Anyone from eZ can help in explaining what the single scripts do and where the cronjob logs are produced? (I have a very big doubt as to which script is responsible for the "publish on approval" too .... is that the workflow one? or is also the notification one involved?) thank you :-) Max
Svitlana Shatokhina	Friday 27 October 2006 7:47:08 am Hi, The "runcronjobs.php" script doesn't modify any ".log" files by default (log files are located in the "var/log" directory). If you need this, run the script using both "-d" and "--logfiles" parameters: php runcronjobs.php -d -s your_siteaccess --logfiles Best regards, Sveta P.S. Sorry, I didn't observe that you already use both parameters..
Svitlana Shatokhina	Wednesday 22 November 2006 2:27:23 am Hi, >...what's the subtreeexpirycleanup.php file used for? If you are using the "cache-block" template function with the "subtree_expiry" parameter to cache the contents of a template block, this cache block will only expire if an object is published below the given subtree (instead of the entire content node tree). The "DelayedCacheBlockCleanup" setting located in the "[TemplateSettings]" section of the "site.ini" configuration file controls whether expired cache blocks with the "subtree_expiry" parameter will be removed immediately or not. If this setting is enabled, the expired cache blocks must be removed manually or using the "subtreeexpirycleanup.php" cron job script. >Anyone from eZ can help in explaining what the single scripts do and where the cronjob logs are produced? The cron job scripts will be documented soon. Best regards, Sveta P.S. http://ez.no/doc/ez_publish/technical_manual/3_8/features/cronjobs

Author

Message

Massimiliano Bariola

Wednesday 14 June 2006 9:08:32 am

Hi,

I never needed to activate the cronjobs until now. So I gave it a few runs from CLI to see if all was ok before trying to cron them.

I ran it with

php runcronjobs.php -s flc_test_user --logfiles -d --sql

I was unable to understand _where_ those logfiles are produced, but it seems that the subtreeexpirycleanup.php script is taking AGES to execute - I am talking about 1.5 hours. Site has about 30000 content objects and makes extensive use of cache-blocks. but as far as I know, cache-blocks are automatically invalidated and regenerated on demand.

So my question is .... what's the subtreeexpirycleanup.php file used for? So far, my site has worked well without it, but I am beginning to think I am missing something here. can I safely omit it? and if so, _when should I be using it instead?

Anyone from eZ can help in explaining what the single scripts do and where the cronjob logs are produced? (I have a very big doubt as to which script is responsible for the "publish on approval" too .... is that the workflow one? or is also the notification one involved?)

thank you :-)

Max

Svitlana Shatokhina

Friday 27 October 2006 7:47:08 am

Hi,

The "runcronjobs.php" script doesn't modify any ".log" files by default (log files are located in the "var/log" directory). If you need this, run the script using both "-d" and "--logfiles" parameters:

php runcronjobs.php -d -s your_siteaccess --logfiles

Best regards,
Sveta

P.S. Sorry, I didn't observe that you already use both parameters..

Svitlana Shatokhina

Wednesday 22 November 2006 2:27:23 am

Hi,

>...what's the subtreeexpirycleanup.php file used for?

If you are using the "cache-block" template function with the "subtree_expiry" parameter to cache the contents of a template block, this cache block will only expire if an object is published below the given subtree (instead of the entire content node tree). The "DelayedCacheBlockCleanup" setting located in the "[TemplateSettings]" section of the "site.ini" configuration file controls whether expired cache blocks with the "subtree_expiry" parameter will be removed immediately or not. If this setting is enabled, the expired cache blocks must be removed manually or using the "subtreeexpirycleanup.php" cron job script.

>Anyone from eZ can help in explaining what the single scripts do and where the cronjob logs are produced?

The cron job scripts will be documented soon.

Best regards,
Sveta

P.S. http://ez.no/doc/ez_publish/technical_manual/3_8/features/cronjobs

eZ debug

Timing:	Jan 18 2025 20:56:35
Script start
Timing:	Jan 18 2025 20:56:35
Module start 'layout'
Timing:	Jan 18 2025 20:56:35
Module start 'content'
Timing:	Jan 18 2025 20:56:35
Module end 'content'
Timing:	Jan 18 2025 20:56:35
Script end

Main resources:

Total runtime	0.0256 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0082	588.1563	152.6563
Module start 'layout'	0.0082	0.0047	740.8125	39.5078
Module start 'content'	0.0130	0.0095	780.3203	89.4922
Module end 'content'	0.0225	0.0031	869.8125	34.3047
Script end	0.0255		904.1172

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0052	20.4554	14	0.0004
Check MTime	0.0030	11.7404	14	0.0002
Mysql Total
Database connection	0.0017	6.5470	1	0.0017
Mysqli_queries	0.0050	19.5813	3	0.0017
Looping result	0.0000	0.1247	1	0.0000
Template Total	0.0020	7.8	1	0.0020
Template load	0.0012	4.6656	1	0.0012
Template processing	0.0008	3.1203	1	0.0008
Override
Cache load	0.0009	3.4480	1	0.0009
General
dbfile	0.0030	11.6929	8	0.0004
String conversion	0.0000	0.0419	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs