Re: apache MaxClients and locking up

2007-02-09 Thread John ORourke
Thanks for all the advice guys - due to pressure from the customer I'm going to concentrate on optimising the app and then look into the server optimisations. It's suffering from inner-platform-effect at the moment (http://thedailywtf.com/forums/69415/ShowPost.aspx ) so the DB is doing way too

Re: apache MaxClients and locking up

2007-02-09 Thread Kjetil Kjernsmo
On Thursday 08 February 2007 17:42, Jonathan Vanasco wrote: > Are you using a 2 sever setup, where mp runs on an alternate port and >   something on port 80 (or elsewhere on the LAN) proxies the request > ? If not, try setting that up.  That can squeeze out some > performance. You could just have a

Re: apache MaxClients and locking up

2007-02-08 Thread Jonathan Vanasco
On Feb 8, 2007, at 8:31 AM, Perrin Harkins wrote: Apache will accept more connections but they will just get queued. This is described in the docs for the MaxClients setting. What makes you think the server is doing nothing? Maybe it's simply waiting for slow database results. Have you tried

Re: apache MaxClients and locking up

2007-02-08 Thread Perrin Harkins
On 2/8/07, John ORourke <[EMAIL PROTECTED]> wrote: Occasionally the DB gets a bit bogged down and starts taking a while to respond (optimisations are being done at the mo), and after a while in the error log I get: [Wed Feb 07 12:35:53 2007] [error] server reached MaxClients setting, consider ra

apache MaxClients and locking up

2007-02-08 Thread John ORourke
Hi folks, Not sure if this is mod_perl related but the logic goes I've never had this issue on a non-mod_perl server... I've got a busy server with quite a few problems, but one in particular is very odd. Occasionally the DB gets a bit bogged down and starts taking a while to respond (opti