From d7a28c8e58fea890c759cc33cd38ab83a7c526c6 Mon Sep 17 00:00:00 2001 From: Bob Beck Date: Wed, 29 Sep 1999 06:30:11 +0000 Subject: Apache 1.3.9 + Mod_ssl 2.4.2 - now builds with apaci nastiness. --- usr.sbin/httpd/htdocs/manual/misc/perf-tuning.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'usr.sbin/httpd/htdocs/manual/misc/perf-tuning.html') diff --git a/usr.sbin/httpd/htdocs/manual/misc/perf-tuning.html b/usr.sbin/httpd/htdocs/manual/misc/perf-tuning.html index 956a7febbc5..46995c9eccd 100644 --- a/usr.sbin/httpd/htdocs/manual/misc/perf-tuning.html +++ b/usr.sbin/httpd/htdocs/manual/misc/perf-tuning.html @@ -209,12 +209,12 @@ consider tuning these settings. Use the mod_status output as a guide.

Related to process creation is process death induced by the -MaxRequestsPerChild setting. By default this is 30, which -is probably far too low unless your server is using a module such as -mod_perl 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. +MaxRequestsPerChild 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.

When keep-alives are in use, children will be kept busy doing nothing waiting for more requests on the already open -- cgit v1.2.3