Closed
Bug 1355415
Opened 8 years ago
Closed 8 months ago
Telemetry for urgent-start utilization
Categories
(Core :: Networking: HTTP, enhancement, P5)
Core
Networking: HTTP
Tracking
()
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: mayhemer, Unassigned)
References
Details
(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.
Updated•8 years ago
|
Whiteboard: [necko-active]
Comment 1•7 years ago
|
||
honza has cdp proj ownership and can reassign as apropos..
Assignee: nobody → honzab.moz
Comment 2•7 years ago
|
||
Bulk priority update: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P4 → P1
Updated•7 years ago
|
Priority: P1 → P2
Whiteboard: [necko-active]
Reporter | ||
Comment 3•7 years ago
|
||
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
Updated•7 years ago
|
Whiteboard: [necko-triaged]
Reporter | ||
Updated•7 years ago
|
Priority: P2 → P5
Updated•2 years ago
|
Severity: normal → S3
Comment 4•8 months ago
|
||
Probably difficult to record what comment 0 says.
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•