Monday 23 August 2004 10:34:27 am

Ed, how much memory is allocated to PHP? Also, what is the PHP script timeout setting? Both are set in the php.ini.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Tuesday 24 August 2004 7:01:54 am

Hrrrm, I'm afraid that is a bit beyond my scope - I was hoping for a quick answer for you. Sorry. Perhaps someone else will pop in and help out.

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Tuesday 24 August 2004 9:52:55 pm

Ed,

It sounds like (and the numbers look like) you don't have all eZ publish cache variables enabled.

Time accumulators:
<snip />
Accumulator Elapsed Percent Count Average
Load cache 0.5689 sec 19.5200% 5 0.1138 sec
Template Total 0.7754 sec 26.6% 1 0.7754 sec
Template load 0.6519 sec 22.3659% 1 0.6519 sec
<snip />
Cache load 0.6178 sec 21.1960% 1 0.6178 sec
Total script time: 2.9145 sec

The eZ Pub runs very responsibly after I followed / created this FAQ:

Configure and Maintain Production Cache with eZ Publish
http://ezpub.co.uk/faqs/development/configure_and_maintain_production_cache_with_ez_publish

It's (currently only) written from the user site perspective but the same settings could easily be placed in your sitestyle_admin/site.ini.append.php

Give it a shot and let us all know about the results.

//kracker
DJ Shadow : The Private Press : Fixed Income

<b>the eZ Pub : http://ezpub.co.uk/</b>

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

Wednesday 25 August 2004 12:00:19 am

Ed,

this sounds very similar to a problem we had recently. For some reason eZ publish figured that it should compile the templates ( atleast some of them ) on every pageload ( unless the page is cached ).

The reason for this was that the time of the server was "older" than the time of the template files. Hence eZ publish thought that the template files were changed and re-compiled the templates. Then on the next page load the template files were still modified in the future compared to the stored compiled templates so a re-compile of the templates was done again. This happens over and over again until the local time of the server catches up with the date/time of the template files.

Please check your server for time skew problems and come back to us so we can write up a FAQ entry for this question. This is a thing which typically can happen when moving an eZ publish installation between servers which are not 100% time synced.

--bård

Documentation: http://ez.no/doc

Wednesday 25 August 2004 1:49:41 am

Ed,

the date of the database server should not have anything to do with this.

The time of the first load is heavy the reason for this is the template compilation which is beeing done. I would recommend that you pre-compile all templates for all used site accesses using the command line tool eztc. More information about that can be found here:
http://www.ez.no/ez_publish/documentation/development/scripting/supplied_scripts/template_compiler

Since you're running FreeBSD I should also mention that eZ publish does perform much better on Linux. This is due to that stat calls--file i/o when e.g. files are included in PHP--which is very slow on FreeBSD. When tuning a high performance server for eZ publish we've actually gotten twice the speed from Linux vs FreeBSD in a multi cpu environment. But this slowdown should definetly not be as long as you experience.

--bård

Documentation: http://ez.no/doc

Wednesday 25 August 2004 2:57:57 am

Ed, the eztc script works nicely in the admin interface as well. The difference between the admin and website is actually just the templates and permissions, you can e.g. make an intranet with all admin functions on the "user site".

These numbers you are gettins is defenetly what you would expect with the hardware you are running on.

We are also working on improving clustering with eZ publish. We have a project going now to improve the cluster for ez.no which will be added to eZ publish when it's done. For clustering the database we will use MySQL clustering functionality, which means that we will have a local MySQL running on all cluster machines. It will of course handle fail safe situations when servers go down.

--bård

Documentation: http://ez.no/doc

Wednesday 25 August 2004 3:26:28 am

Don't feel bad Ed,

It happens to the best of us. I like reading your threads & posts :)
I think that besides your specific troubles, several very interesting
subjects were discussed in this thread.

I think that these will be useful to others in the future. Not as
long term as other threads but very topical for the era, every day
we are "making history".

You can't waste my time, only I can do that :)

Regards,
kracker

The Matrix Revolutions : OST : In My Head

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

Tuesday 31 January 2006 11:26:01 am

Hi,

We're having similar issues... we have a real slow load time within the admin interface.. clients complain about the speed issue.

I've got the public facing site cached pretty well.. loads at about 1 sec but the admin interface takes more than 5sec and even worse when you're editing content.

We're having this on 2 different sites and eZ versions... they are: 3.6.0 and 3.6.2

Any ideas on how to further optmize admin site?

Regards,
Fabricio

http://www.solobromasychistes.com <<Joomla Site :P
http://www.recipesforhealthyfood.com/ <<Drupal Site :P
http://www.ezforge.com/ <<future ezCommunity, Articles, forums and more...