Re: Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

[Norbert Elbanbuena <norbert@xxxxxxxxxxxxxx>]

So from what I understand, Apache status will display more than minimum server limit but will add more once spare threads is hitting the threshold.

I currently have 18 childs with 64 threads per child but I should expect to see more child processes spawned if there are less than 800 idle workers. Idle workers are spare threads identified as "_" Waiting for Connection.

Does this sound right?

Regards,

Norbert E.

---

From: Eric Covener <covener@xxxxxxxxx>
Sent: Monday, April 26, 2021 9:27 AM
To: users@xxxxxxxxxxxxxxxx <users@xxxxxxxxxxxxxxxx>
Subject: Re: Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

 

On Mon, Apr 26, 2021 at 9:53 AM Norbert Elbanbuena <norbert@xxxxxxxxxxxxxx> wrote:

Hi,

I attempted to tune Apache's configuration, and used below settings:

<IfModule mpm_event_module>

ThreadsPerChild 64

MaxRequestWorkers 1600

MinSpareThreads 800

MaxSpareThreads 1600

ServerLimit 25

MaxConnectionsPerChild 0

</IfModule>

But checking /server-status I only see Max workers up to 1152

Server uptime: 11 hours 20 minutes 35 seconds

Server load: 0.15 0.15 0.21

Total accesses: 57926 - Total Traffic: 279.6 MB - Total Duration: 50642985

CPU Usage: u35.7 s29.44 cu0 cs0 - .16% CPU load

1.42 requests/sec - 7.0 kB/second - 5060 B/request - 874.27 ms/request

130 requests currently being processed, 1022 idle workers

I think this is showing you that there are currently 16 64-thread processes.  The numbers might not be perfectly round because the server is not frozen while mod_status iterates over everything.

Apache will spin up a 17th process when there are less than 800 idle threads.