From: Luca Toscano Date: Sat, 18 Jun 2016 10:23:16 +0000 (+0000) Subject: Documentation rebuild X-Git-Tag: 2.4.22~7 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=70ab2364f581ae8ae87132d681186c0ad49430bd;p=thirdparty%2Fapache%2Fhttpd.git Documentation rebuild git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1748952 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mpm_common.html.en b/docs/manual/mod/mpm_common.html.en index 0085cd421ee..a92386d608b 100644 --- a/docs/manual/mod/mpm_common.html.en +++ b/docs/manual/mod/mpm_common.html.en @@ -279,6 +279,13 @@ in *BSDs. then make each child handle a single bucket (with round-robin distribution of the buckets at children creation time).

+

Meaning of "online" CPU core

+

On Linux (and also BSD) a CPU core can be turned on/off if + Hotplug + is configured, therefore ListenCoresBucketsRatio needs to + take this parameter into account while calculating the number of buckets to create.

+
+

ListenCoresBucketsRatio can improve the scalability when accepting new connections is/becomes the bottleneck. On systems with a large number of CPU cores, enabling this feature has @@ -288,7 +295,10 @@ in *BSDs.

There must be at least twice the number of CPU cores than the configured ratio for this to be active. The recommended ratio is 8, hence at least 16 - cores should be available at runtime when this value is used.

+ cores should be available at runtime when this value is used. + The right ratio to obtain maximum performance needs to be calculated + for each target system, testing multiple values and observing the variations in your + key performance metrics.

top