From 5d3ff9d193561e3761a235c622246d4b2ed6bec7 Mon Sep 17 00:00:00 2001 From: "Kyle J. McKay" Date: Sun, 4 Oct 2015 06:31:34 -0700 Subject: [PATCH] apache.conf.in: warn about MaxProcesses + TerminationScore interaction Signed-off-by: Kyle J. McKay --- apache.conf.in | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/apache.conf.in b/apache.conf.in index ab39946..7059f53 100644 --- a/apache.conf.in +++ b/apache.conf.in @@ -196,7 +196,14 @@ # Note that adding a 'MaxProcesses ...' option here may be valuable # to limit the maximum number of gitweb.cgi processes that can be # spawned (default is 100) -- perhaps to something much lower such - # as 1 or 2 times the number of CPU cores. + # as 1 or 2 times the number of CPU cores. Also note that in the + # unlikely event all the children finish their 100 requests at the + # same time, the server's FcgidSpawnScoreUpLimit should be set + # to at least 3 times the MaxProcesses value chosen to allow them + # all to respawn immediately. It MUST be at least twice the chosen + # MaxProcesses value (assuming FcgidTerminationScore is still the + # default 2) in order to allow any child to respawn at all without + # a delay. FcgidCmdOptions @@cgiroot@@/gitweb.cgi \ MaxRequestsPerProcess 100 IOTimeout 300 -- 2.11.4.GIT