ProcessCaching enabled degrades performance

Author Message

Paul Borgermans

Thursday 10 April 2003 10:32:38 am

Weird

When I set ProcessCaching enabled, the time needed to generate a page almost doubles!

Is the meaning of "enabled" here reversed or am I missing something?

BTW, best performance until now with php accelerator (ioncube) +
[Templatesettings]
NodeTreeCaching=enabled
ProcessCaching=disabled

The slowest combination of these 3 parameters gives a whoppy 0.8 sec versus 0.21 sec for the fastest combination with the accelerator (machine used: Dual PIII 1.8 Ghz, SCSI disk subsystem, SuSE Linux).

Template processing still takes the most time (40-60%)

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Jan Borsodi

Friday 11 April 2003 6:57:16 am

Process caching is not done yet so it's really not adviced to use it. Once it is done (or at least improved) the processing times of templates will decrease significantly.

Tree caching only removes the parsing stage of the template engine, meaing that the template tree is cached as a PHP array ready for use.

--
Amos

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

Paul Borgermans

Friday 11 April 2003 10:42:09 am

Thanks Jan

I hope these speedups make it for the 3.1 release. Right now, around 5-10 pages per second seems to be the limit on recent machinery with ezp. No doubt, load in the future (large collaborative sites) may grow well beyond this for our projects.

Regards

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Tony Wood

Friday 11 April 2003 10:52:37 am

Paul,

I'm getting around 70 pages per minute on hardware of a similar spec to yours... I have viewcaching turned on and node and process caching turned off... Are your pages doing some heavy duty work?

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Paul Borgermans

Friday 11 April 2003 11:32:26 am

Well 70 pages per minute or per second?

Here an average page takes around 0.2 to 0.35 sec to be generated. So something like 100-150 pages per minute is currently a reasonable figure.

But I expect for some sites to go up to 20-30 pages per second, so the (granular) caching efficiency will be very important to sustain such scenarios as it consumes the bulk of the processing time.

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Tony Wood

Friday 11 April 2003 11:40:25 am

Arh... Sorry Paul I misread... been a long day.

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 31 2025 01:15:50
Script start
Timing: Jan 31 2025 01:15:50
Module start 'layout'
Timing: Jan 31 2025 01:15:50
Module start 'content'
Timing: Jan 31 2025 01:15:50
Module end 'content'
Timing: Jan 31 2025 01:15:50
Script end

Main resources:

Total runtime0.0238 sec
Peak memory usage4,096.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0054 588.3828151.2422
Module start 'layout' 0.00540.0034 739.6250220.7500
Module start 'content' 0.00880.0136 960.37501,005.8672
Module end 'content' 0.02240.0014 1,966.242237.9922
Script end 0.0238  2,004.2344 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002610.7435140.0002
Check MTime0.00114.7036140.0001
Mysql Total
Database connection0.00083.231110.0008
Mysqli_queries0.00218.704930.0007
Looping result0.00000.046010.0000
Template Total0.00104.110.0010
Template load0.00073.113010.0007
Template processing0.00021.015310.0002
Override
Cache load0.00051.967610.0005
General
dbfile0.00114.614580.0001
String conversion0.00000.030040.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_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