On Fri, 4 Mar 2005 00:00:58 +1100, Tig <tigger.on@xxxxxxxxx> wrote: > My understading (which may be wrong) is that the server is running out > of free processors, therefore queuing requests, which is why the > server is very slow to respond. Apache has 1024 allowed, and has > simply run out processors. The high CPU usage is a side-effect of > this. I don't actually see evidence of high CPU usage. I see a high load average, but that is not the same thing. > > My questions are, why are the sleepers not being dropped quicker, or > being re-used? Check mod_status's server-status page to see what the processes are doing. If you find that many are in KeepAlive state, then you can probably increase throughput by reducing KeepAliveTimeout. > Should the MinSpareServer or MaxSpareServers (or both) be increased? No, these would likely have no effect (or even a harmeful effect). > > Should the ServerLimit (and MaxClients) be increased, to handle the > load or decreased, as it appears a chunk of swap is being used? I'm not an expert on this stuff, but the swap usage suggests to me that you are short of memory, in which case you will want to *reduce* MaxClients to get the best performance. > > Should the MaxRequestsPerChild be given a value, to help drop the > sleeping processors quicker? This will not help unless you have a memory leak. > > Is it simply the hardware can not handle the load? Possibly. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|