You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Arnab Ganguly <ag...@gmail.com> on 2007/05/07 12:07:00 UTC
[users@httpd] one more on MaxRequestPerChild
Hi All,
Is it possible that Apache launches a new process due to overlaod even
before the MaxRequestPerChild is met?
Thanks
-A
Re: [users@httpd] one more on MaxRequestPerChild
Posted by Jim Jagielski <ji...@jaguNET.com>.
On May 7, 2007, at 6:07 AM, Arnab Ganguly wrote:
> Hi All,
> Is it possible that Apache launches a new process due to overlaod
> even before the MaxRequestPerChild is met?
> Thanks
> -A
Apache will always try to maintain an idle pool of processes/threads
between Min/MaxSpareServers|Threads, so it will create or kill
processes/threads in order to achieve that. Assuming you have
not hit MaxClients and Apache needs to create more process/threads
to handle the load, yes, it will do do. As things slow down it
will also kill off idle threads/processes to maintain
the correct size idle pool.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org