Open
Bug 1522593
Opened 4 years ago
Updated 6 months ago
Collect timing data for network requests that includes time spent on trips through the service worker, for profiling purposes
Categories
(Core :: DOM: Service Workers, enhancement, P2)
Core
DOM: Service Workers
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox66 | --- | affected |
People
(Reporter: mstange, Unassigned)
References
Details
In profiles such as http://bit.ly/2DwFvG2 , it's hard to tell at what stages a given network request spent time. Especially if a network request goes through a service worker, and back to the content main thread event loop etc.
I'd like us to collect a breakdown of all stages that such a request goes through, including all queuing times in various event loops, so that we can display those times in the profiler on a given request.
Comment 1•4 years ago
|
||
The priority flag is not set for this bug and there is no activity for 2 weeks.
:overholt, could you have a look please?
Flags: needinfo?(overholt)
Comment 2•4 years ago
|
||
The team's really close to landing a big refactoring of the network interception code but we can definitely add some instrumentation once that lands and sticks.
Flags: needinfo?(overholt)
Priority: -- → P2
Updated•6 months ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•