How fast should eZ Publish be...

«

Previous topic

|

|

Next topic

»

Author	Message
Sebastian Picklum	Saturday 28 January 2006 7:00:24 am ...on a shared hosting account which is advertised as an "eZ Publish Hosting" account? With all caches on, I get a total script running time of about 0,4 to 0,6 (in some cases 1,75) secs for the "plain_user" demo with every feature enabled. Is this okay or do I have to complain? Regards, Sebastian sp@php.net
Gabriel Ambuehl	Saturday 28 January 2006 1:23:15 pm If the host doesnt use a PHP accelerator (which IMHO it should for an ezpublish hosting deal but maybe that's just my opinion), that sounds about right. It's otherwise not all too bad either, I get about 0.2s on a dedicated box used only by myself and your box surely will be shared. Visit http://triligon.org
Sebastian Picklum	Saturday 28 January 2006 1:53:00 pm Hi Gabriel! Thanks for your information! This is without a PHP-Accelerator as the hosting company runs PHP in CGI-Mode (very strange...). But 5 bucks for 12Gigs of eZp-driven Webspace is still a great deal though... :-) Regards, Sebastian sp@php.net
Gabriel Ambuehl	Saturday 28 January 2006 2:00:28 pm CGI mode helps with security if done right. And for that, 0.5s is actually fast ;) Visit http://triligon.org
Steph A	Sunday 29 January 2006 7:40:01 am As Gabriel said - you should be very happy with 0,5 sec. I also had some sites running on shared servers, just as you. But I NEVER got under 1,5 sec loadtime. But if they advertise as "ez hosts" they really should be using a accelerator ... my opinion anyway :) Im now running a dedicated server with php-accelerator... AMD Sempron(tm) 2400+ (686-class CPU) 1666.49- MHz RAM: 239,94 MB ... loadtime is 0,14sec - and I pay 29 bucks a month :D
liu spider	Sunday 29 January 2006 11:02:06 pm could you tell me where can I find the deal "5 bucks for 12Gigs of eZp-driven Webspace" thanks http://liucougar.scim-im.org SCIM Input Method Platform http://scim.sf.net SJSD Online Editor http://sf.net/projects/sjsd
Sebastian Picklum	Sunday 29 January 2006 11:23:17 pm I could, but that would surely against the forum rules. But to tell you in advance: The are running <b>CGI</b> mode which requires some tweaking of eZ Publish to get all features up and running. e.g. the WebDAV-Server doesn't work in standard CGI setups. Regards Sebastian sp@php.net

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:25:56
Script start
Timing:	Jan 31 2025 01:25:56
Module start 'layout'
Timing:	Jan 31 2025 01:25:56
Module start 'content'
Timing:	Jan 31 2025 01:25:56
Module end 'content'
Timing:	Jan 31 2025 01:25:56
Script end

Main resources:

Total runtime	0.0284 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	588.1250	151.2109
Module start 'layout'	0.0064	0.0047	739.3359	220.6875
Module start 'content'	0.0111	0.0155	960.0234	1,001.6797
Module end 'content'	0.0266	0.0017	1,961.7031	37.9922
Script end	0.0283		1,999.6953

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	11.5701	14	0.0002
Check MTime	0.0013	4.5122	14	0.0001
Mysql Total
Database connection	0.0011	4.0399	1	0.0011
Mysqli_queries	0.0026	9.0202	3	0.0009
Looping result	0.0000	0.0630	1	0.0000
Template Total	0.0013	4.5	1	0.0013
Template load	0.0010	3.4087	1	0.0010
Template processing	0.0003	1.0648	1	0.0003
Override
Cache load	0.0007	2.3120	1	0.0007
General
dbfile	0.0004	1.2606	8	0.0000
String conversion	0.0000	0.0277	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