On Mon, Feb 15, 2010 at 7:19 AM, Zdravko Spoljar <zdravko.spoljar@xxxxxxxxxxxx> wrote: > > hi all, > > we have busy web site and for last few weeks we have problem with apache > processes eat all memory (that is problem, but not topic here). > I attempt to control problem by lowering ServerLimit (documentation states > that is max number of apache processes). > > ServerLimit is at 75 (confirmed by /server-info as active value), but 'ps auxw' > show around 90-95 processes. process creation times are within 10 minutes. > i was try to report that as bug (in my view it is), but i got redirected here. :) Read the fourth paragraph at http://httpd.apache.org/docs/2.2/mod/worker.html#how-it-works > here is part of server config as-is: > > <IfModule mpm_worker_module> > ServerLimit 75 > ThreadLimit 30 > StartServers 11 > MinSpareThreads 45 > MaxSpareThreads 95 > ThreadsPerChild 25 > MaxClients 1500 > MaxRequestsPerChild 500 > </IfModule> Anything that causes child processes to exit during steady state can lead to extra child processes *when some requests take a relatively long time to finish*. Your very low value for MaxRequestsPerChild is the likely culprit. You might have to increase MaxSpareThreads as well since that will cause one or more child processes to begin termination when load decreases by a moderate amount. --------------------------------------------------------------------- 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
|