Forums / Developer / Cache block optimization

Cache block optimization

Author Message

Antoine W.

Wednesday 10 August 2005 6:51:36 am

Hello everybody,
I'm trying to optimize my pagelayout with cache-blocks, and I have a few questions :
* Is it possible to set a cache block with more than one path for subtree_expiry ?
Something like :

{cache-block subtree_expiry=array('products/','services/')}
...
{/cache-block}

* Is it possible to set a cache block to expire only when specified classes will be published/deleted/updated ?
Something like :

{cache-block class_identifier_expiry=array('product','service')}
...
{/cache-block}

Thanks ! ;)

eZ debug

Timing: Jan 31 2025 04:26:04
Script start
Timing: Jan 31 2025 04:26:04
Module start 'content'
Timing: Jan 31 2025 04:26:04
Module end 'content'
Timing: Jan 31 2025 04:26:04
Script end

Main resources:

Total runtime0.0248 sec
Peak memory usage2,048.0000 KB
Database Queries4

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0072 587.9297180.8359
Module start 'content' 0.00720.0076 768.765689.8828
Module end 'content' 0.01480.0099 858.648466.7031
Script end 0.0247  925.3516 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002510.0850120.0002
Check MTime0.00114.2818120.0001
Mysql Total
Database connection0.00083.287710.0008
Mysqli_queries0.003815.441640.0010
Looping result0.00000.068220.0000
Template Total0.009337.510.0093
Template load0.00114.233810.0011
Template processing0.008333.259410.0083
Override
Cache load0.00083.194510.0008
General
dbfile0.005220.8760100.0005
String conversion0.00000.027930.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1pagelayout.tpl<No override>extension/sevenx/design/simple/templates/pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs