top
, and divide this into your total available memory,
leaving some room for other processes."> Hello All,The expected symptom is that Apache is unresponsive to additional
>
> This is regarding production servers. Recently Apache server hit MaxClient
> settings; resulting in crash of sites. However, sites was back to normal
> after restarting Apache.
requests until some of the child processes finish what they're working
on.
Restarting Apache without increasing MaxClients isn't helpful; if it
is a hard restart it trashes the current connections.
Run apachectl -V to see the limit; it should be in the tens of thousands.
> I read about MaxClient settings and increase it from 200 to 250 (as I read
> somewhere that 256 is a limit).
(I'm trying to get a public URL for the slides I sent you privately
> Since then sites are working fine. But still
> I see average concurrent request on Apache is 180-200 which sometime goes to
> 220 as well. This is threatening, as we are planning to put more sites live
> on same Apache.
>
> Therefore, I am considering to increase MaxClient in order to handle
> "at-least" 600 concurrent request.
>
> I will be grateful if somebody can assist me in setting the right values for
> ServerLimit, MaxClient, MinSpareServers and MaxSpareServers.
which offer some advice here.)
That's workload-specific. Here are some interesting notes from
> Also, what
> maximum values I can have for MaxClients (want to know max concurrent users
> Apache can handle.)
someone playing with a similar box a few years ago:
http://www.stdlib.net/~colmmacc/2006/03/23/niagara-vs-ftpheanetie-showdown/
---------------------------------------------------------------------
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