Closed Bug 1355415 Opened 7 years ago Closed 3 months ago

Telemetry for urgent-start utilization


(Core :: Networking: HTTP, enhancement, P5)




Tracking Status
firefox55 --- affected


(Reporter: mayhemer, Unassigned)



(Whiteboard: [necko-triaged])

The telemetry should give us an idea on how often the urgent-start mechanism helps to unblock a request that would normally be put to a queue.
Whiteboard: [necko-active]
honza has cdp proj ownership and can reassign as apropos..
Assignee: nobody → honzab.moz
Bulk priority update:
Priority: P4 → P1
Priority: P1 → P2
Whiteboard: [necko-active]
So, I don't see an easy way to implement a telemetry that would reliably say "marking this request as urgent made it to be dispatched XXX ms sooner".  We can have some kind of imperfect one (still hard to implement) that may not be giving exact numbers.  I may also spend one or two DAYS to implement something that will be 95-99% accurate.  But I think demoing this via a synthetic test is a better time investment for now.

Releasing.  Leaving the priority until we have a different mechanism showing UrgentStart marking has a positive impact.
Assignee: honzab.moz → nobody
Whiteboard: [necko-triaged]
Priority: P2 → P5
Severity: normal → S3

Probably difficult to record what comment 0 says.

Closed: 3 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.