Pipeline Project Tracking Bug

RESOLVED INCOMPLETE

Status

()

Core
Networking: HTTP
--
enhancement
RESOLVED INCOMPLETE
7 years ago
8 months ago

People

(Reporter: mcmanus, Assigned: mcmanus)

Tracking

(Depends on: 1 bug)

Trunk
x86_64
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

7 years ago
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.
(Assignee)

Updated

7 years ago
Depends on: 603505
(Assignee)

Updated

7 years ago
Depends on: 603506
(Assignee)

Updated

7 years ago
Depends on: 603508
(Assignee)

Updated

7 years ago
Depends on: 603512
(Assignee)

Updated

7 years ago
Depends on: 603513
(Assignee)

Updated

7 years ago
Blocks: 603514
(Assignee)

Updated

7 years ago
No longer blocks: 603514
Depends on: 603514
(Assignee)

Comment 1

7 years ago
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.
(Assignee)

Comment 2

7 years ago
Created attachment 488490 [details] [diff] [review]
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.
(Assignee)

Updated

7 years ago
Depends on: 615342
No longer depends on: 255141
(Assignee)

Updated

7 years ago
Depends on: 599164
(Assignee)

Updated

7 years ago
Depends on: 613977
(Assignee)

Comment 3

7 years ago
Created attachment 495147 [details] [diff] [review]
connection, latency, and pipelining statistics v2
Attachment #488490 - Attachment is obsolete: true
(Assignee)

Updated

7 years ago
Assignee: nobody → mcmanus
(Assignee)

Updated

6 years ago
Depends on: 542401
(Assignee)

Updated

6 years ago
Depends on: 61977, 632496, 632419, 631801, 632948
No longer depends on: 613977
(Assignee)

Updated

6 years ago
Depends on: 623948
No longer depends on: 632948

Comment 4

6 years ago
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.

Updated

6 years ago
Blocks: 585196
Depends on: 652308
Depends on: 659760
(Assignee)

Updated

2 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.