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


(Core :: DOM: Service Workers, enhancement, P2)




Tracking Status
firefox66 --- affected


(Reporter: mstange, Unassigned)



In profiles such as , 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.

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)

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
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.