eZ Community » Forums » Install & configuration » Server overload when EzPublish is...
expandshrink

Server overload when EzPublish is running

Server overload when EzPublish is running

Friday 06 April 2012 4:29:51 pm - 4 replies

Hi there,

this is not a real EZ Publish issue (I suppose), but it's a system issue!

I moved my site from a local host (a small PC that I use as a server) to a remote host with a real powerful server (4 processors, 4GB Ram).

The site seems to work fine, but the system administrator told me that there's something strange with the server load. 

Calling "top" on a linux shell I see that at least 2 apache processes takes 100% of processor time. The average server load is always around 2.0!

The system administrator told me to check if there's something strange with apache/mysql session management... but I did not modify nothing of the standard EZPublish configuration!

 

My last and unique technical intervention on the machine has been a little modify on the apache2.conf file: I set Startservers 3 under prefork MPM and Startservers 1 under Worker MPM, to avoid a proliferation of apache2 processes.

Any idea?

 

Thanks

Friday 06 April 2012 6:32:00 pm

Check your server and eZ Publish error log (tail -f var/log/error.log).

Good luck!

Friday 06 April 2012 6:53:47 pm

Hello

do you have stats about your website: if the website is too busy : it can be the reason.

the second reason i see  is do you put cache on ?

 

see you and dont give up

Alex

 

 

Monday 09 April 2012 12:48:47 am

Hi Simone,

I would suggest you to isolate the reason for your serverload:

  1. 2 apache processes ???
  2. whats you MySQL Server doing?
  3. is it related to your eZ instance?
  4. maybe its about your templates?
  5. some ini-config on extensions are killing your performance?

Fortunately you have serveraccess.

Just some ideas, hope this helps to tame the beast blunk.gif Emoticon

Best
Chris

Wednesday 11 April 2012 10:44:14 am

Default Apache settings for the prefork stuff are not that bad, try first to re-set the old configuration, then tell us what's in your logs. On a production server, the error.log file should be (most of the time) empty. Even if you have warnings (such as "this variable is already defined"blunk.gif Emoticon then you must fix these issue since writing these warnings in the error log kills the performance

Also, have you checked these parameters ?

  • TemplateCache should be enabled
  • TemplateCompile should be enabled
  • ViewCaching should be enabled
  • AlwaysLog should not log other things than errors

Is your website under a high load (give us a estimation of the page viewed per seconds) ?

In your admin interface, go to /setup/info and tell us what you see about these parameters :

  • PHP Accelerator
  • Memory limit

When enabling debug output, with all the cache enabled, how many SQL requests are needed to render a page ?

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu