administration interface very slow

Author Message

Fabio Carissimi

Thursday 01 February 2007 12:31:58 am

Hi,

I have a question regarding performance of the administration interface,
we have APC php cache, we changed the settings for MySQL like described
in the article Tuning MySQL for eZ Publish cf 'http://ez.no/community/articles/tuning_mysql_for_ez_publish'
(again thanks to Bård Farstad), but the administration interface is very (too) slow.

I also tried to install an extension for the tree menu : ezjaxx, which improves performance,
but it is not enough.

What can we do for this ?

The server is a blade HS20 on a blade center IBM Architecture, with the following characteristics :
dual *Intel Xeon 3.20GHz
3Go RAM,
HARD DRIVE SCSI 10000 rpm
NETWORK 1Gb/s
*data is on a SAN Qlogic driver

Software versions are :
php 4.3.9-cgi (4.3.9-3.22) (on red hat AS 4 uptodate)
Apache 2.0.52
mysql 4.1.20

Thanks for help
Fabio Carissimi

Łukasz Serwatka

Thursday 01 February 2007 12:50:58 am

Hi Fabio,

What timings do you have in debug output? Your PHP installed is as CGI or Apache module?

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Fabio Carissimi

Thursday 01 February 2007 1:41:15 am

Hi Lukasz,

as a timing extract I have

<b>Timing points:</b>
<i>Checkpoint Elapsed Rel. Elapsed Memory Rel. Memory</i>
Module start 'content' 0.0000 sec 0.2997 sec 6,483.4063KB 7,281.9297KB
Module end 'content' 0.2997 sec 0.9590 sec 13,765.3359KB 6,885.5391KB
End 1.2587 sec 20,650.8750KB 0.0059KB
<b>Total runtime: 1.2880 sec</b>
<b>Time accumulators:</b>
<i> Accumulator Elapsed Percent Count Average</i>
<b>ini_load</b>
Load cache 0.0270 sec 2.0189% 16 0.0017 sec
FindInputFiles 0.0208 sec 1.5580% 16 0.0013 sec
<b>Mysql Total</b>
Mysql_queries 0.0983 sec 7.3527% 97 0.0010 sec
Looping result 0.0081 sec 0.6056% 88 0.0001 sec
<b>TS translator </b>
TS init 0.0150 sec 1.1237% 13 0.0012 sec
TS cache load 0.0104 sec 0.7773% 13 0.0008 sec
TS context load 0.0074 sec 0.5527% 13 0.0006 sec
<b>Template Total 1.2343 sec 92.3% 3 0.4114 sec</b>
Template load 0.0121 sec 0.9048% 3 0.0040 sec
Template processing 1.2215 sec 91.3571% 3 0.4072 sec
Template load and register function 0.0001 sec 0.0094% 1 0.0001 sec
<b>override </b>
Cache load 0.0112 sec 0.8359% 6 0.0019 sec
Matching rules 0.0012 sec 0.0884% 3 0.0004 sec
<b>class_abstraction </b>
Instantiating content class attribute 0.0065 sec 0.4851% 6 0.0011 sec
<b>General </b>
dbfile 0.0441 sec 3.2954% 639 0.0001 sec
<b>Total script time: 1.3370 sec</b>

What seems to be heavy is Template processing 1.2215 sec 91.3571%
but I have this settings :

[TemplateSettings]
TemplateCache=enabled
TemplateCompile=enabled
TemplateOptimization=enabled

I have php 4.3.9 CGI like sais in the first post,
we work on a linux Red Hat AS 4 and we must use certified versions,
and unfortunatly, certified version on this OS is 4.3.9 CGI and not last php4 as an apache module.
Do you think it can change a lot ?

Łukasz Serwatka

Thursday 01 February 2007 2:07:54 am

How big is content structure tree in admin interface? What are timings when it is collapsed? You can tune it in contentstructuremenu.ini (reduce items showed in menu)

For maximum performance and stability we recommend PHP as Apache (prefork) module for eZ Publish.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Fabio Carissimi

Thursday 01 February 2007 2:22:49 am

The site contains more than 1000 nodes /objects, but I put a limit to 500 in the tree menu in contentmenustructure.ini (MaxNodes=500). but for this point, I think ezjaxx extension partially solve the problem ??

here is an example of a scipt that take more than 7 seconds, it is only a content view in the admin
interface :
<b>Timing points:</b>
<i>Checkpoint Elapsed Rel. Elapsed Memory Rel. Memory</i>
Module start 'content' 0.0000 sec 2.8035 sec 6,487.5469Kb 19,424.4609Kb
Module end 'content' 2.8035 sec 4.3842 sec 25,912.0078Kb 16,497.3672Kb
End 7.1878 sec 42,409.3750Kb 0.0156Kb
<b>Total runtime</b>: 7.3141 sec
<b>Time accumulator</b>s:
<i>Accumulator Elapsed Percent Count Average</i>
<b>ini_load</b>
Load cache 0.0329 sec 0.4464% 19 0.0017 sec
FindinputFiles 0.0255 sec 0.3459% 19 0.0013 sec
<b>Mysql Total</b>
Mysql_queries 0.6537 sec 8.8766% 1311 0.0005 sec
Looping result 0.1193 sec 1.6206% 1304 0.0001 sec
<b>TS translator</b>
TS init 0.0182 sec 0.2466% 15 0.0012 sec
TS cache load 0.0130 sec 0.1770% 15 0.0009 sec
TS context load 0.0096 sec 0.1301% 15 0.0006 sec
<b>Template Total</b> 7.1698 sec 97.4% 3 2.3899 sec
Template load 0.0124 sec 0.1690% 3 0.0041 sec
Template processing 7.1566 sec 97.1830% 3 2.3855 sec
String conversion in template resource 0.0004 sec 0.0049% 1 0.0004 sec
Template parser: create text elements 0.0008 sec 0.0114% 1 0.0008 sec
Template parser: remove whitespace 0.0002 sec 0.0030% 1 0.0002 sec
Template parser: construct tree 0.0042 sec 0.0570% 1 0.0042 sec
Template load and register function 0.0008 sec 0.0107% 3 0.0003 sec
<b>override</b>
Cache load 0.0874 sec 1.1863% 81 0.0011 sec
Matching rules 0.0012 sec 0.0165% 3 0.0004 sec
<b>class_abstraction</b>
instantiating content class attribute 0.1075 sec 1.4592% 91 0.0012 sec
Sytem overhead
Fetch class attribute name 0.0641 sec 0.8700% 54 0.0012 sec
Fetch class attribute can translate value 0.0014 sec 0.0188% 1 0.0014 sec
XML
image XML parsing 0.0112 sec 0.1526% 2 0.0056 sec
<b>General</b>
<b>dbfile</b> 0.2093 sec 2.8424% 3117 0.0001 sec
String conversion 0.0011 sec 0.0153% 16 0.0001 sec
String conversion w/ mbstring 0.0001 sec 0.0011% 1 0.0001 sec
<b>Total script time</b>: 7.3641 sec

Thanks for help

stephane couzinier

Thursday 01 February 2007 3:53:51 pm

I have the same trouble but only when the template are not compile.
if I reload the page, the total time take only 2 s (with all debug activate, will be better if disable)

Do you have the same time when you reload the page?

don't flush the cache

Xavier Dutoit

Friday 02 February 2007 3:02:19 am

What ez publish version do you use ?

What's the speed without compile enabled (it should be faster the first page load after a clear cache).

Yes CGI has a had the reputation to be slower. I worked on a lighttpd+fastcgi config and it works fine (that's my dev environment). This being said, the numbers you give a high, no matter what. Try to disable the content tree to have a speed info not related to the size of your content tree.

X+

http://www.sydesy.com

Fabio Carissimi

Friday 02 February 2007 3:35:19 am

If I reload the same page, it takes also 1-2 seconds,
but If I request this same page after an hour, it takes again 7-8 seconds

Content tree limitations + extensions have improved performance, but I think we should try to use PHP as an Apache module
to see the difference

to answer Xavier
I use ezpublish 3.8.3 and it is the same timing without compile enabled

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