search

roberthodasz / mod-spdy

Automatically exported from code.google.com/p/mod-spdy
0 stars 0 forks source link

mod_status details #54

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It'd be nice if mod_spdy had the ability to report its details in mod_status's 
/server-status or something similar.  

Currently, it seems to even mask the number of requests actually being 
processed.  

For example, if I load a heavy page that should take mod_spdy a while to load, 
and visit the /server-status page for the proxy and only see my request for the 
/server-status page listed, whereas the backend (not running mod_spdy since 
it's currently still mod_php and needs mpm-prefork) shows the numerous requests 
being processed.

Let me know if you need anymore details.

Thanks,
Brian

Original issue reported on code.google.com by bpkr...@gmail.com on 25 Sep 2012 at 8:17

GoogleCodeExporter commented 9 years ago 
Reporting mod_spdy status information via mod_status seems like a good idea.

You are right that individual SPDY streams (requests) within a SPDY connection 
are not reported on the mod_status scoreboard.  This is because these requests 
execute within mod_spdy's private thread pool rather than within the MPM's 
threads/processes, so there's no way for the MPM scoreboard to know about them.

However, with some work, I would think that mod_spdy could be made to maintain 
its own scoreboard-like structure, tracking active SPDY connections and their 
streams.  It could then report that information on the /server-status page 
using mod_status's status_hook.

Can you give me an idea of what data would be useful to be able to see?  Do you 
want the same S/R/W/etc request status for every stream in every SPDY 
connection, the way the scoreboard gives you for normal HTTP requests?  Or do 
you just want to know, say, the number of currently active SPDY streams, so 
that you know how many requests you are processing?  Is there any other 
SPDY-specific status info that would be useful to get on /server-status?

Original comment by mdste...@google.com on 25 Sep 2012 at 9:59

GoogleCodeExporter commented 9 years ago 
We tend to use the data in /server-status to graph site activity and server 
load, as well as look at it manually for more detailed responses when things 
are reported as having problems, so yeah the same level of detail on 
per-request status and scoreboard counts would be good.  I wonder if there 
would be a way to single out which requests were being handled by spdy vs. the 
usual route.

On top of that, I think having a notion of how mod_spdy's internal thread pool 
resources are being used could give a good idea for admins on how they might 
want to tune those values.

Thanks,
Brian

Original comment by bpkr...@gmail.com on 25 Sep 2012 at 10:19

GoogleCodeExporter commented 9 years ago 
Is there any update on this?

Thanks,
Brian

Original comment by bpkr...@gmail.com on 25 Sep 2013 at 3:21