> Am 03.12.2021 um 13:27 schrieb Eric Covener <cove...@gmail.com>:
> 
> On Thu, Dec 2, 2021 at 4:41 AM Stefan Eissing <ste...@eissing.org> wrote:
>> 
>> Friends of the scoreboard,
>> 
>> trying to improve the mod_http2 information available on our scoreboard, I 
>> am not sure I can interpret correctly what I see. Maybe someone can help me?
>> 
>> I run a 2.4.51 and see what worker are busy with. That#s fine. But I also 
>> see slots where the connection has been closed a while ago and still this is 
>> listed.
>> 
>> The overall stats are
>> 
>> Slot    PID     Stopping        Connections     Threads Async connections
>> total   accepting       busy    idle    writing keep-alive      closing
>> 0       69336   no      1       yes     1       24      0       0       0
>> 1       69338   no      0       yes     0       25      0       0       0
>> Sum     2       0       1               1       49      0       0       0
>> 
>> which means only the connection who reads server-status is active. But I 
>> also see listings as in:
>> 
>> Srv  PID   Acc    M CPU  SS  Req Dur Conn Child Slot Client        Protocol 
>> VHost         Request
>> ...
>> 1-1  69338 0/0/10 _ 0.00 948 0   5   0.0  0.00  0.04 195.133.18.60 http/1.1 
>> domain.com:80 GET /up.php HTTP/1.1
>> 
>> The "SS" of 948 keeps on climbing, but the connection is long gone. How is 
>> one supposed to read that? Is that a side effect of an MPM event change that 
>> switches slots on re-activation?
> 
> Sorry, I read this on mobile and lost track. A "M[ode] of "_" is idle
> and "SS" in this case tells you how long the slot has been idle. The
> request details are just the details from "SS" ago that used this slot
> and completed.

Thanks. I had now a more closer look at the code and how the stats are 
collected. As Niklas said, the scoreboard lost usefulness in mpm_event with 
lots of distracting "ghost" entries displayed when slots are switched. At least 
I know now that it is not a fluke in my recent H2 implementation.

Cheers,
Stefan

Reply via email to