enterprise-support team mailing list archive

[ Christian Ehrhardt  <1628278@xxxxxxxxxxxxxxxxxx>]

This seems to not have been important enough for anybody to work on :-/
But I thought I could recheck this today and I think the issue is resolved:

<IfModule mpm_worker_module>
        StartServers                     2
        MinSpareThreads          80
        MaxSpareThreads          200
        ThreadLimit              500
        ThreadsPerChild          250
        MaxRequestWorkers        4000
        MaxConnectionsPerChild   0
</IfModule>

ps -eLf | grep ^www-data | wc -l
252
That is 250 workers plus 2 base processes

With the slowtest running:
$ slowhttptest -c 20000 -H -g -o my_header_stats-20k -i 10 -r 2000 -t GET -u http://localhost/ -x 24 -p 3
I get much more spawned:
ps -eLf | grep ^www-data | wc -l
4032

That is the max limit of 4k that I set and a few other processes that manage them.
Unfortunately I don't know when exactly, but in recent Ubuntu versions this is fixed.

** Changed in: apache2 (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to apache2 in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1628278

Title:
  mpm_worker has a limit of 64 ThreadsPerChild even if you configure it
  with a larger number

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1628278/+subscriptions