Hmm.. I wonder; what is cachetreshold?

Previous topic

Developer

Next topic

Author	Message
Valentin Svelland	Thursday 09 October 2003 7:16:48 am My site.ini of eZ v.3.2 has this parameter: # The threshold for file cleanup, if it is exceeded a global expiry is used instead # The value is calculated with the number of affected nodes * viewmodes * translations * sitedesign CacheThreshold=120 I've read the comments but I can't quite see the logic.. What happens if I increase the value to 200 for example? Maybe a silly question, but I am a silly man... :) (I'm really searching for a way to speed up my site. The caching works fine, but it seems like it's cache is renewed to often. This makes the site appear slow to my very few visitors.)
Jan Borsodi	Thursday 16 October 2003 1:36:38 am It is used to determine if the view cache files should be cleared immediately or if it ALL view caches should be expired. The reason for this is if you have a large tree and change one of the top level items then the view cache for all the items must be clear. However if the number of subitems is large it would take a long time before all of them is cleared. To remedy this we calculate a cache value, we multiply the number of subitems by the number viewmodes by the number of translations by the number of sitedesigns. If this number is larger then the threshold we only do the simple expiration. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Valentin Svelland

Thursday 09 October 2003 7:16:48 am

My site.ini of eZ v.3.2 has this parameter:

# The threshold for file cleanup, if it is exceeded a global expiry is used instead
# The value is calculated with the number of affected nodes * viewmodes * translations * sitedesign
CacheThreshold=120

I've read the comments but I can't quite see the logic.. What happens if I increase the value to 200 for example? Maybe a silly question, but I am a silly man... :)

(I'm really searching for a way to speed up my site. The caching works fine, but it seems like it's cache is renewed to often. This makes the site appear slow to my very few visitors.)

Jan Borsodi

Thursday 16 October 2003 1:36:38 am

It is used to determine if the view cache files should be cleared immediately or if it ALL view caches should be expired.

The reason for this is if you have a large tree and change one of the top level items then the view cache for all the items must be clear. However if the number of subitems is large it would take a long time before all of them is cleared.

To remedy this we calculate a cache value, we multiply the number of subitems by the number viewmodes by the number of translations by the number of sitedesigns. If this number is larger then the threshold we only do the simple expiration.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

eZ debug

Timing:	Jan 31 2025 06:27:37
Script start
Timing:	Jan 31 2025 06:27:37
Module start 'layout'
Timing:	Jan 31 2025 06:27:37
Module start 'content'
Timing:	Jan 31 2025 06:27:37
Module end 'content'
Timing:	Jan 31 2025 06:27:37
Script end

Main resources:

Total runtime	0.0135 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.0048	588.1406	151.2109
Module start 'layout'	0.0048	0.0024	739.3516	36.6641
Module start 'content'	0.0072	0.0048	776.0156	90.1563
Module end 'content'	0.0120	0.0015	866.1719	29.9922
Script end	0.0135		896.1641

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	17.6995	14	0.0002
Check MTime	0.0010	7.7583	14	0.0001
Mysql Total
Database connection	0.0007	4.9927	1	0.0007
Mysqli_queries	0.0021	15.8116	3	0.0007
Looping result	0.0000	0.0812	1	0.0000
Template Total	0.0011	8.0	1	0.0011
Template load	0.0008	5.8139	1	0.0008
Template processing	0.0003	2.1864	1	0.0003
Override
Cache load	0.0005	3.9472	1	0.0005
General
dbfile	0.0003	2.0363	8	0.0000
String conversion	0.0000	0.0583	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