From: Luca Toscano Date: Sat, 18 Jun 2016 10:23:01 +0000 (+0000) Subject: Added some information to ListenCoresBucketsRatio documentation page already in trunk. X-Git-Tag: 2.4.22~8 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3b7a36ce643a0ae49b5bab5de1957e5a886d8f3c;p=apache Added some information to ListenCoresBucketsRatio documentation page already in trunk. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1748951 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mpm_common.xml b/docs/manual/mod/mpm_common.xml index af03c93e80..dbc9b78a7d 100644 --- a/docs/manual/mod/mpm_common.xml +++ b/docs/manual/mod/mpm_common.xml @@ -276,6 +276,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 @@ -285,7 +292,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.