603503 - Pipeline Project Tracking Bug

Status: RESOLVED INCOMPLETE

(Core :: Networking: HTTP, enhancement)

Description

[Patrick McManus [:mcmanus]]

This is a patch tracking bug for the HTTP pipeline project. There are several interesting meta-pipeline bugs but I'm trying to keep the scope of this one to just the patches that are needed for the project - to the extent that those patches address specific other bugzilla entries they can be maintained as dependencies of the patch bug.

Comment 1

[Patrick McManus [:mcmanus]]

Little bit of a milestone to note here - all the code related depending bugs have patches attached to them.. still need a test infrastructure and LOTS of measure/tweak/remeasure to do.

Comment 2

[Patrick McManus [:mcmanus]]

Attachment: connection, latency, and pipelining statistics

This is a handy, if horrifically ugly, patch for getting a bunch of statistics about network timing. (not to be nominated for merging.. but fyi).

It gives the distribtuion of handshake rtt's, http transaction latency distribution (further broken down by class of transaction), queue time before being sent on the network (again, break down by class), the distribution of number of transactions on a connection, the split between how transactions are dispatched (new conn vs pconn reuse vs pipeline) again broken down by class, the rate at which we create backup connections (and the hit rate at which we utilize them), the distribution of pipeline depths broken down by class, the state of the pipeline-governor at dispatch time, and the distribution of negative feedback events broken down by class.

I suppose eventually it could be rolled into test pilot somehow, but for now it just dumps a whole bunch of data when the connection manager dtors. Like I said, not nominated for inclusion but really useful if you want to try out the patches underneath this tracking bug.

Comment 3

[Patrick McManus [:mcmanus]]

Attachment: connection, latency, and pipelining statistics v2

Comment 4

[(dormant account)]

I started a basic reporting extension in the telemetry bug. You need to expose these stats either via idl or extern "C" so they can be accessed from javascript.