Tune apache2 for more concurrent connections: Difference between revisions
From Open-Xchange
Line 1: | Line 1: | ||
=The problem= | =The problem= | ||
By default apache2 is configured to support | By default apache2 is configured to support 150 concurrent connections. | ||
This forces all | 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. | |||
=The solution= | =The solution= |
Revision as of 07:50, 14 December 2011
The problem
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.
The solution
This is an example configuration to provide 800 concurrent connections. Please ensure that your apache is using the mpm_worker 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.
<IfModule mpm_worker_module> ServerLimit 25 StartServers 10 MinSpareThreads 75 MaxSpareThreads 250 ThreadLimit 64 ThreadsPerChild 32 MaxClients 800 MaxRequestsPerChild 0 </IfModule>
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. |
MaxClients | 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 MaxClients and reloading the configuration. |
MaxRequestsPerChild | Defines the number of Connections that a process can handle during its lifetime (keep-alives are counted once). After that it will be killed. |
For further information on these parameters see http://httpd.apache.org/docs/2.2/mod/worker.html and http://httpd.apache.org/docs/2.2/mod/mpm_common.html.
--Steffen.templin 12:10, 23 May 2011 (UTC)