Tune apache2 for more concurrent connections

Apache Configuration

MPM Module

Please ensure that your apache is using the mpm_worker or mpm_event module. This allows us to serve lots of concurrent connections by using less RAM than with mpm_prefork as we are going to start much less processes. Unfortunately the default MPM module seems to differ from distro to distro, so doublecheck and make sure you are on the right setting.

The method to configure the MPM module differes of course also from distribution to distribution:

• CentOS7/RHEL7: adjust /etc/httpd/conf.modules.d/00-mpm.conf
• Debian: use a2dismod / a2enmod to disable the wrong and enable the desired MPM Module.

About mpm_worker vs mpm_event: we assume they are equivalent for our purpose. mpm_worker is the older one and just works fine. mpm_event should improve on it further but we have been unable to observe any actual advantages.

Concurrent Connections

By default apache2 is configured to support 150 concurrent connections. This forces all parallel requests beyond that limit to wait. Especially if, for example, active sync clients maintain a permanent connection for push events to arrive.

This is an example configuration to provide 8000 concurrent connections.

<IfModule mpm_worker_module>
    ServerLimit              250
    StartServers              10
    MinSpareThreads           75
    MaxSpareThreads          250 
    ThreadLimit               64
    ThreadsPerChild           32
    MaxRequestWorkers       8000
    MaxConnectionsPerChild 10000
</IfModule>

Note: MaxRequestWorkers was previously named MaxClients and MaxConnectionsPerChild was previously named MaxRequestsPerChild. If you are using old (pre 2.4) verions of apache you might need to use the old names.

Short explanation of the parameters:

ServerLimit	Declares the maximum number of running apache processes. If you change this value you have to restart the daemon.
StartServers	The number of processes to start initially when starting the apache daemon.
MinSpareThreads/MaxSpareThreads	This regulates how many threads may stay idle without being killed. Apache regulates this on its own very well with default values.
ThreadsPerChild	How many threads can be created per process. Can be changed during a reload.
ThreadLimit	ThreadsPerChild can be configured as high as this value during runtime. If you change this value you have to restart the daemon.
MaxRequestWorkers	This declares how many concurrent connections we provide. Devided by ThreadsPerChild you get the suitable ServerLimit value. May be less than ServerLimit * ThreadsPerChild to reserve some resources that can be engaged during runtime with increasing MaxRequestWorkers and reloading the configuration.
MaxConnectionsPerChild	Defines the number of Connections that a process can handle during its lifetime (keep-alives are counted once). After that it will be killed. This can be used to prevent possible apache memory leaks. If set to 0 the lifetime is infinite.

For further information on these parameters see http://httpd.apache.org/docs/2.4/mod/worker.html and http://httpd.apache.org/docs/2.4/mod/mpm_common.html.

--Steffen.templin 12:10, 23 May 2011 (UTC)