Does single Apache worker serves only 1 request or more than that

apache-2.2mpm-worker

I am facing a problem in Apache server when the number of users reaches around 250 concurrent. The problem occurred only when the idle worker number was set to 0.

So my question is, does a single Apache worker serves only 1 request or more than that? How can I increase worker or max user to be at least 700 concurrent?

i am using Apache 2.2 on Windows 2008 R2 and MPM type is : mpm_winnt.

Best Answer

mpm_winnt seems to be pretty close in design to mpm_worker. mpm_worker uses several processes (servers) with multiple threads per process to serve connections. mpm_winnt uses just one process.

So, you can tune the number of concurrent connections using ThreadLimit and ThreadsPerChild directives.

Please read the docs before blindly changing those two.

Related Solutions

Apache2 + mod_fastcgi + suexec + php5.2 = unstable on high load

Apache 2.4 offers a new fastcgi proxy module (mod_proxy_fcgi) that can proxy requests to php-fpm. Using mod_proxy as an intermediary means you have access to all the mod_proxy options, including queueing and depletion parameters separate from the main server.

I would advise you to set it up on a test server with the apache 2.4 event MPM and php-fpm; you can tune each php pool for different applications, too.

Linux – Apache spawning hundreds of processes and pushing up load averages

It's the value of your ServerLimit setting and others inside httpd.conf:

StartServers       8
MinSpareServers    5
MaxSpareServers   20
ServerLimit      256
MaxClients       256
MaxRequestsPerChild  4000

Dial down your ServerLimit to 100 or so and decrease MaxRequestPerChild to around 1000 so the children reap faster.

Best Answer

Related Solutions

Apache2 + mod_fastcgi + suexec + php5.2 = unstable on high load

Linux – Apache spawning hundreds of processes and pushing up load averages

Related Topic