Commit b5600a5f authored by Jim Jagielski's avatar Jim Jagielski
Browse files

Document the MaxRequestsPerChild values wrt 

KeepAlives and how to tune it


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@83078 13f79535-47bb-0310-9956-ffa450edef68
parent bac9e514

docs/manual/misc/perf-tuning.html

+6 −6
Original line number Diff line number Diff line
@@ -209,12 +209,12 @@ consider tuning these settings. Use the <CODE>mod_status</CODE> output 
as a guide.



<P>Related to process creation is process death induced by the

<CODE>MaxRequestsPerChild</CODE> setting.  By default this is 30, which

is probably far too low unless your server is using a module such as

<CODE>mod_perl</CODE> which causes children to have bloated memory

images.  If your server is serving mostly static pages then consider

raising this value to something like 10000.  The code is robust enough

that this shouldn't be a problem.

<CODE>MaxRequestsPerChild</CODE> setting.  By default this is 0, which

means that there is no limit to the number of requests handled

per child. If your configuration currently has this set to some

very low number, such as 30, you may want to bump this up significantly.

If you are running SunOS or an old version of Solaris, limit this

to 10000 or so because of memory leaks.



<P>When keep-alives are in use, children will be kept busy

doing nothing waiting for more requests on the already open

docs/manual/mod/core.html

+4 −0
Original line number Diff line number Diff line
@@ -1998,6 +1998,10 @@ number of processes when the server load reduces. 


<P>This directive has no effect on Win32.



<P><STRONG>NOTE:</STRONG> For <EM>KeepAlive</EM> requests, only the first

request is counted towards this limit. In effect, it changes the

behavior to limit the number of <EM>connections</EM> per child.



<P><HR>



<H2><A NAME="maxspareservers">MaxSpareServers directive</A></H2>