jim 99/04/20 15:19:17
Modified: htdocs/manual/misc perf-tuning.html
htdocs/manual/mod core.html
Log:
Document the MaxRequestsPerChild values wrt
KeepAlives and how to tune it
Revision Changes Path
1.17 +6 -6 apache-1.3/htdocs/manual/misc/perf-tuning.html
Index: perf-tuning.html
===================================================================
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/perf-tuning.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- perf-tuning.html 1998/12/18 22:29:56 1.16
+++ perf-tuning.html 1999/04/20 22:19:13 1.17
@@ -209,12 +209,12 @@
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
1.146 +4 -0 apache-1.3/htdocs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/core.html,v
retrieving revision 1.145
retrieving revision 1.146
diff -u -r1.145 -r1.146
--- core.html 1999/02/09 20:20:23 1.145
+++ core.html 1999/04/20 22:19:15 1.146
@@ -1998,6 +1998,10 @@
<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>
