Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

2021-04-26 Thread Norbert Elbanbuena 
Thank you so much I am very clear now!

Regards,

Norbert E.


From: Eric Covener 
Sent: Monday, April 26, 2021 1:40 PM
To: users@httpd.apache.org 
Subject: Re: [users@httpd] Apache max workers in /server-status not same as 
MaxWorkers in mpm_event_module



On Mon, Apr 26, 2021 at 2:28 PM Norbert Elbanbuena 
mailto:norb...@teligentip.com>> wrote:
Hi,

$ ./apachectl -v
Server version: Apache/2.4.46 (Unix)
Server built:   Nov 15 2020 14:32:04

I just accessed /server-status?refresh=5 to regularly refresh the page.
But I think understand the counts better now. My only other question is does 
the Request column retain the last URL requested or does it clear after an x 
amount of time when the thread is idle?
I'm referring to the output below:

Srv PID Acc M   CPU SS  Req Dur ConnChild   
SlotClient  ProtocolVHost   Request
3-0 10941   0/1/1   _   0.00695 1   1   0.0 0.02
0.02192.168.237.61  http/1.1
app3.mytestapp.net:8080 GET 
/server-status?refresh=30 HTTP/1.1
3-0 10941   0/1/1   _   0.01404 0   0   0.0 0.00
0.00127.0.0.1   http/1.1
app3.mytestapp.net:8080 GET 
/manager/status?XML=true HTTP/1.1


It will stay there until the thread is reused or the process goes away. The 
"SS" column tells you how long ago that request shown completed (or started?)

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

2021-04-26 Thread Eric Covener 
On Mon, Apr 26, 2021 at 2:28 PM Norbert Elbanbuena 
wrote:

> Hi,
>
> $ ./apachectl -v
> Server version: Apache/2.4.46 (Unix)
> Server built:   Nov 15 2020 14:32:04
>
> I just accessed /server-status?refresh=5 to regularly refresh the page.
> But I think understand the counts better now. My only other question is
> does the Request column retain the last URL requested or does it clear
> after an x amount of time when the thread is idle?
> I'm referring to the output below:
>
> Srv PID Acc M CPU SS Req Dur Conn Child Slot Client Protocol VHost Request
> *3-0* 10941 0/1/1 _ 0.00 695 1 1 0.0 0.02 0.02 192.168.237.61 http/1.1
> app3.mytestapp.net:8080 GET /server-status?refresh=30 HTTP/1.1
> *3-0* 10941 0/1/1 _ 0.01 404 0 0 0.0 0.00 0.00 127.0.0.1 http/1.1
> app3.mytestapp.net:8080 GET /manager/status?XML=true HTTP/1.1
>

It will stay there until the thread is reused or the process goes away. The
"SS" column tells you how long ago that request shown completed (or
started?)

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

2021-04-26 Thread Norbert Elbanbuena 
Hi,

$ ./apachectl -v
Server version: Apache/2.4.46 (Unix)
Server built:   Nov 15 2020 14:32:04

I just accessed /server-status?refresh=5 to regularly refresh the page.
But I think understand the counts better now. My only other question is does 
the Request column retain the last URL requested or does it clear after an x 
amount of time when the thread is idle?
I'm referring to the output below:

Srv PID Acc M   CPU SS  Req Dur ConnChild   
SlotClient  ProtocolVHost   Request
3-0 10941   0/1/1   _   0.00695 1   1   0.0 0.02
0.02192.168.237.61  http/1.1app3.mytestapp.net:8080 GET 
/server-status?refresh=30 HTTP/1.1
3-0 10941   0/1/1   _   0.01404 0   0   0.0 0.00
0.00127.0.0.1   http/1.1app3.mytestapp.net:8080 GET 
/manager/status?XML=true HTTP/1.1

Regards,

Norbert E.


From: Rodrigo Cunha 
Sent: Monday, April 26, 2021 11:01 AM
To: users@httpd.apache.org 
Subject: Re: [users@httpd] Apache max workers in /server-status not same as 
MaxWorkers in mpm_event_module

Hi, send the inventory this host with S/O version and Apache version.
Send the command and options used for check status.

Tks.

On Mon, Apr 26, 2021 at 10:59 AM Norbert Elbanbuena 
mailto:norb...@teligentip.com>> wrote:
Hi,

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


ThreadsPerChild 64
MaxRequestWorkers 1600
MinSpareThreads 800
MaxSpareThreads 1600
ServerLimit 25
MaxConnectionsPerChild 0


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
SlotPID StoppingConnections Threads Async connections
total   accepting   busyidlewriting keep-alive  closing
0   22539   no  0   yes 0   64  0   0   0
1   22540   no  0   yes 0   64  0   0   0
2   22541   no  0   yes 0   64  0   0   0
3   22743   no  0   yes 0   64  0   0   0
4   22832   no  0   yes 0   64  0   0   0
5   22833   no  3   yes 3   61  0   0   0
6   22974   no  1   yes 2   62  0   0   0
7   22975   no  3   yes 3   61  0   0   0
8   22976   no  5   yes 4   60  0   0   0
9   22983   no  4   yes 4   60  0   0   0
10  23272   no  2   yes 2   62  0   0   0
11  23273   no  6   yes 5   59  0   0   0
12  23274   no  12  yes 10  54  0   1   0
13  23280   no  12  yes 12  52  0   0   0
14  23288   no  14  yes 13  51  0   0   0
15  23300   no  20  yes 19  45  0   0   0
16  23331   no  54  yes 53  11  0   0   0
17  23370   no  0   yes 0   64  0   0   0
Sum 18  0   136 130 10220   1   0

Am I reading it incorrectly?

Regards,

Norbert Elbanbuena


--
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

2021-04-26 Thread Rodrigo Cunha 
Hi, send the inventory this host with S/O version and Apache version.
Send the command and options used for check status.

Tks.

On Mon, Apr 26, 2021 at 10:59 AM Norbert Elbanbuena 
wrote:

> Hi,
>
> I attempted to tune Apache's configuration, and used below settings:
>
> 
> ThreadsPerChild 64
> MaxRequestWorkers 1600
> MinSpareThreads 800
> MaxSpareThreads 1600
> ServerLimit 25
> MaxConnectionsPerChild 0
> 
>
> But checking /server-status I only see Max workers up to 1152
>
> Server uptime: 11 hours 20 minutes 35 secondsServer load: 0.15 0.15 0.21Total
> accesses: 57926 - Total Traffic: 279.6 MB - Total Duration: 50642985CPU
> Usage: u35.7 s29.44 cu0 cs0 - .16% CPU load1.42 requests/sec - 7.0
> kB/second - 5060 B/request - 874.27 ms/request130 requests currently
> being processed, 1022 idle workers
> Slot PID Stopping Connections Threads Async connections
> total accepting busy idle writing keep-alive closing
> 0 22539 no 0 yes 0 64 0 0 0
> 1 22540 no 0 yes 0 64 0 0 0
> 2 22541 no 0 yes 0 64 0 0 0
> 3 22743 no 0 yes 0 64 0 0 0
> 4 22832 no 0 yes 0 64 0 0 0
> 5 22833 no 3 yes 3 61 0 0 0
> 6 22974 no 1 yes 2 62 0 0 0
> 7 22975 no 3 yes 3 61 0 0 0
> 8 22976 no 5 yes 4 60 0 0 0
> 9 22983 no 4 yes 4 60 0 0 0
> 10 23272 no 2 yes 2 62 0 0 0
> 11 23273 no 6 yes 5 59 0 0 0
> 12 23274 no 12 yes 10 54 0 1 0
> 13 23280 no 12 yes 12 52 0 0 0
> 14 23288 no 14 yes 13 51 0 0 0
> 15 23300 no 20 yes 19 45 0 0 0
> 16 23331 no 54 yes 53 11 0 0 0
> 17 23370 no 0 yes 0 64 0 0 0
> Sum 18 0 136   130 1022 0 1 0
> Am I reading it incorrectly?
>
> Regards,
>
> Norbert Elbanbuena
>


-- 
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

2021-04-26 Thread Norbert Elbanbuena 
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 
Sent: Monday, April 26, 2021 9:27 AM
To: users@httpd.apache.org 
Subject: Re: [users@httpd] 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 
mailto:norb...@teligentip.com>> wrote:
Hi,

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


ThreadsPerChild 64
MaxRequestWorkers 1600
MinSpareThreads 800
MaxSpareThreads 1600
ServerLimit 25
MaxConnectionsPerChild 0


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.

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

2021-04-26 Thread Eric Covener 
On Mon, Apr 26, 2021 at 9:53 AM Norbert Elbanbuena 
wrote:

> Hi,
>
> I attempted to tune Apache's configuration, and used below settings:
>
> 
> ThreadsPerChild 64
> MaxRequestWorkers 1600
> MinSpareThreads 800
> MaxSpareThreads 1600
> ServerLimit 25
> MaxConnectionsPerChild 0
> 
>
> But checking /server-status I only see Max workers up to 1152
>



Server uptime: 11 hours 20 minutes 35 secondsServer load: 0.15 0.15 0.21Total
> accesses: 57926 - Total Traffic: 279.6 MB - Total Duration: 50642985CPU
> Usage: u35.7 s29.44 cu0 cs0 - .16% CPU load1.42 requests/sec - 7.0
> kB/second - 5060 B/request - 874.27 ms/request130 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.

[users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

2021-04-26 Thread Norbert Elbanbuena 
Hi,

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


ThreadsPerChild 64
MaxRequestWorkers 1600
MinSpareThreads 800
MaxSpareThreads 1600
ServerLimit 25
MaxConnectionsPerChild 0


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
SlotPID StoppingConnections Threads Async connections
total   accepting   busyidlewriting keep-alive  closing
0   22539   no  0   yes 0   64  0   0   0
1   22540   no  0   yes 0   64  0   0   0
2   22541   no  0   yes 0   64  0   0   0
3   22743   no  0   yes 0   64  0   0   0
4   22832   no  0   yes 0   64  0   0   0
5   22833   no  3   yes 3   61  0   0   0
6   22974   no  1   yes 2   62  0   0   0
7   22975   no  3   yes 3   61  0   0   0
8   22976   no  5   yes 4   60  0   0   0
9   22983   no  4   yes 4   60  0   0   0
10  23272   no  2   yes 2   62  0   0   0
11  23273   no  6   yes 5   59  0   0   0
12  23274   no  12  yes 10  54  0   1   0
13  23280   no  12  yes 12  52  0   0   0
14  23288   no  14  yes 13  51  0   0   0
15  23300   no  20  yes 19  45  0   0   0
16  23331   no  54  yes 53  11  0   0   0
17  23370   no  0   yes 0   64  0   0   0
Sum 18  0   136 130 10220   1   0

Am I reading it incorrectly?

Regards,

Norbert Elbanbuena