From ae1582f9a7f3fca571a3c7d9d4241d43e751882f Mon Sep 17 00:00:00 2001 From: Christophe Jaillet Date: Fri, 24 Aug 2018 20:49:43 +0000 Subject: [PATCH] Add a note in ThreadsPerChild about the relationship with ThreadsLimit. + add a missing link git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1838958 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mpm_common.xml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/manual/mod/mpm_common.xml b/docs/manual/mod/mpm_common.xml index d1e09eeed5..6508ca7e49 100644 --- a/docs/manual/mod/mpm_common.xml +++ b/docs/manual/mod/mpm_common.xml @@ -270,7 +270,7 @@ in *BSDs.

A ratio between the number of (online) CPU cores and the number of listeners' buckets can be used to make Apache HTTP Server create num_cpu_cores / ratio listening buckets, each containing its - own Listen-ing socket(s) on the same port(s), and + own Listen-ing socket(s) on the same port(s), and then make each child handle a single bucket (with round-robin distribution of the buckets at children creation time).

@@ -812,6 +812,12 @@ per child process

The default value for ThreadsPerChild is 64 when used with mpm_winnt and 25 when used with the others.

+ +

The value of ThreadsPerChild can not exceed the + value of ThreadsLimit. If a + higher value is configured, it will be automatically reduced at start-up + and a warning will be logged. The relationship between these 2 directives + is explained in ThreadsLimit.

-- 2.50.1