ProcessCaching enabled degrades performance

Next topic

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