Httpd worker MPM Configuration: Difference between revisions
| (3 intermediate revisions by the same user not shown) | |||
| Line 58: | Line 58: | ||
Even if [[#ServerLimit|ServerLimit]] is set to a high value ([[#ThreadsPerChild|ThreadsPerChild]] left to default), the number of concurrent connection ''is'' limited by [[#MaxClients.2C_MaxRequestWorkers|MaxClients]]. This was tested and proven. | Even if [[#ServerLimit|ServerLimit]] is set to a high value ([[#ThreadsPerChild|ThreadsPerChild]] left to default), the number of concurrent connection ''is'' limited by [[#MaxClients.2C_MaxRequestWorkers|MaxClients]]. This was tested and proven. | ||
The general workings of the worker MPM are described in the [[Httpd worker MPM Concepts#MaxClients|worker MPM concepts page]]. | |||
==Reaching the Upper Limit== | |||
The server detects the fact that the MaxClients limit has been reached and logs this in the error log: | |||
<pre> | |||
[error] server reached MaxClients setting, consider raising the MaxClients setting | |||
</pre> | |||
==MaxClients Idiosyncrasies== | ==MaxClients Idiosyncrasies== | ||
| Line 146: | Line 156: | ||
Minimum and maximum number of idle threads available to handle request spikes. Both values are server-wide - apply to all processes. The MinSpareThreads default value is 75. | Minimum and maximum number of idle threads available to handle request spikes. Both values are server-wide - apply to all processes. The MinSpareThreads default value is 75. | ||
If there aren't enough idle threads in the server then child processes are created until the number of idle threads is greater than number. For a detailed explanation of how these parameters work, see {{Internal|Httpd worker MPM Concepts# | If there aren't enough idle threads in the server then child processes are created until the number of idle threads is greater than number. For a detailed explanation of how these parameters work, see {{Internal|Httpd worker MPM Concepts#spare|worker MPM Concepts}} | ||
Latest revision as of 04:43, 9 January 2017
Internal
Overview
Configuration Example
<IfModule worker.c>
StartServers 4
ServerLimit 16
ThreadLimit 50
ThreadsPerChild 50
MinSpareThreads 50
MaxSpareThreads 300
MaxRequestsPerChild 0
MaxClients 300
</IfModule>
Diagram
The configuration elements described below are represented on the mod_jk Concepts Diagram.
Sizing Procedure
Enabling worker MPM Mode
If you configure httpd yourself, make sure you compiled it with worker MPM support.
If you use Red Hat EWS, worker support comes pre-compiled into $APACHE_HOME/sbin/httpd.worker, make sure the start script is using that.
For more details about compiling httpd with the right MPM mode, see:
MaxClients, MaxRequestWorkers
"MaxClients" and "MaxRequestWorkers" are equivalent, since 2.3.13 "MaxClients" was renamed "MaxRequestWorkers", but for the time being, both names are valid and supported.
MaxClients represents the maximum number of connections that will be processed simultaneously by the entire server, seen as the sum of all active children processes. The default value is 400 = 16 (ServerLimit) * 25 (ThreadsPerChild). The directive restricts the total number of threads that will be available to serve clients.
Any connection attempts over the MaxClients limit will normally be queued, up to a number based on the ListenBacklog directive. Once a child process becomes available after handling at least one of its current requests, the connection will then be serviced.
Even if ServerLimit is set to a high value (ThreadsPerChild left to default), the number of concurrent connection is limited by MaxClients. This was tested and proven.
The general workings of the worker MPM are described in the worker MPM concepts page.
Reaching the Upper Limit
The server detects the fact that the MaxClients limit has been reached and logs this in the error log:
[error] server reached MaxClients setting, consider raising the MaxClients setting
MaxClients Idiosyncrasies
- MaxClients must be at least equals with ThreadsPerChild. If not, httpd will warn at startup and automatically adjust the value to be equals with ThreadsPerChild.
- MaxClients must be an integer multiple of ThreadsPerChild. If it's not, it will be adjusted automatically, and the server will issue an error message similar to the one presented below:
MaxClients (12) is not an integer multiple of ThreadsPerChild (10), lowering MaxClients to 10
ServerLimit
Upper limit on configurable number of httpd processes. Default is 16. It is a hard limit, any attempts to change this directive during a restart will be ignored.
Note: if ServerLimit is n, ps will show n + 2 server processes. For a ServerLimit value of 1:
[webr@rangiroa ~]$ ps -ef | grep httpd root 7535 1 0 11:15 ? 00:00:00 /home/webr/httpd-2.2.21-worker/bin/httpd -k start webr 7536 7535 0 11:15 ? 00:00:00 /home/webr/httpd-2.2.21-worker/bin/httpd -k start webr 7537 7535 0 11:15 ? 00:00:00 /home/webr/httpd-2.2.21-worker/bin/httpd -k start
The first one (7535) is the parent that manages the children that perform the work. It is root-owned. What is the second one (7536)? The third one (7537) is the actual child.
If ServerLimit is set to a value much higher than necessary, unused shared memory will be allocated. If both ServerLimit and MaxClients are set to values higher than the system can handle, Apache may not start or the system may become unstable.
Use this directive only if your MaxClients and ThreadsPerChild settings require more than 16 server processes (default). Do not set the value of this directive any higher than the number of server processes required by what you may want for MaxClients and ThreadsPerChild.
StartServers
The StartServers directive sets the number of child server processes created on startup. Default is 3. As the number of processes is dynamically controlled depending on the load, there is usually little reason to adjust this parameter.
ThreadsPerChild and ThreadLimit
ThreadsPerChild directive sets the number of threads created by each child process. The child creates these threads at startup and never creates more. Default in 25. The value of ThreadsPerChild can be modified during a graceful restart or a hard restart, however it cannot be set to a value over ThreadLimit.
The ThreadLimit directive sets the maximum configured value for ThreadsPerChild for the lifetime of the httpd process. Any attempts to change this directive during a restart will be ignored. The default value is 64. There is a hard limit of ThreadLimit 20000 hardcoded into the server. To increase it even further past this limit, you will need to modify the value of MAX_THREAD_LIMIT in the mpm source file and rebuild the server.
It is possible to configure ThreadsPerChild to a value higher than ThreadLimit, httpd won't complain at startup but the value will be silently ignored and each child will actually create 'ThreadLimit' threads.
For clarity, it's probably best to explicitly configure ThreadLimit and ThreadsPerChild to the same value.
ThreadsPerChild influences the number of connections maintained by the proxy workers in their pool. For more details see mod_proxy Connection Pooling.
ThreadLimit Idiosyncrasies
Declare ThreadLimit before MaxClients in the configuration file. Doing otherwise would lead to someting similar to (for the below, ThreadLimit was set to 100, but declared after MaxClients):
ServerLimit 16 StartServers 16 MaxClients 10 ThreadLimit 100 ThreadsPerChild 100
starting httpd ... WARNING: ThreadsPerChild of 100 exceeds ThreadLimit value of 64 threads, lowering ThreadsPerChild to 64. To increase, please see the ThreadLimit directive.
ListenBacklog
The maximum length of the queue of pending connections. See the backlog parameter to the listen(2) system call. Default 511. This will often be limited to a smaller number by the operating system. This varies from OS to OS. Also note that many OSes do not use exactly what is specified as the backlog, but use a number based on (but normally larger than) what is set.
MaxRequestsPerChild
Limit on the number of requests that an individual child server will handle during its life. After MaxRequestsPerChild requests, the child process will die. If MaxRequestsPerChild is 0, then the process will never expire. Setting MaxRequestsPerChild to a non-zero value limits the amount of memory that process can consume by (accidental) memory leakage.
The default (compiled-in) value of this setting (10000) is used when no MaxRequestsPerChild directive is present in the configuration. Many default configurations provided with the server include "MaxRequestsPerChild 0" as part of the default configuration.
MinSpareThreads, MaxSpareThreads
Minimum and maximum number of idle threads available to handle request spikes. Both values are server-wide - apply to all processes. The MinSpareThreads default value is 75.
If there aren't enough idle threads in the server then child processes are created until the number of idle threads is greater than number. For a detailed explanation of how these parameters work, see