Closed Bug 1693074 Opened 3 years ago Closed 2 years ago

Adding telemetries to measure the critical path of ServiceWorker Performance


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




93 Branch
Tracking Status
firefox93 --- fixed


(Reporter: edenchuang, Assigned: edenchuang)


(Blocks 1 open bug)



(5 files, 1 obsolete file)

Knowing how long registration loading blocked the main thread for the initialization of ServiceWorkerManager which was the delta between "getRegistrationsDone" and "getRegistrationsWaiting" in

Knowing how long we blocked waiting for the directory lock for the underlying Cache API storage for the ServiceWorker which was teh delta between "ready" and "start" in

Knowing how long it took between the "spawn" request ( for the (remote) ServiceWorker (as perceived in the parent process) and the "creationSucceeded" ( (which covers the top level script evaluation as well)

Knowing how long it takes the navigation "fetch" event to be responded to: currently I get that from the time between "asyncOpenInternal" on the intercepted channel ( and the "startSynthesizedResponse" (

Knowing how long it takes for that response to be pumped into the chanel, which is basically the time between startSynthesizedResponse and onStopRequest (

Assignee: nobody → echuang
Severity: -- → S2
Priority: -- → P2
Attachment #9206329 - Attachment description: Bug 1693074 - P1 Adding telemetries for measuring performance ServiceWorker register flow/ → Bug 1693074 - P1 Adding telemetries for measuring performance ServiceWorker register flow

Eden, are you actively working on this? Thanks!

Flags: needinfo?(echuang)
Attachment #9206329 - Attachment is obsolete: true
Attached file
Flags: needinfo?(echuang)
Attachment #9235591 - Flags: data-review?(mmccorquodale)
Attachment #9235591 - Flags: data-review?(mmccorquodale) → data-review?(chutten)

Comment on attachment 9235591 [details]


Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?


Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

If the request is for permanent data collection, is there someone who will monitor the data over time?

Yes, Eden Chuang is responsible.

Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1, Technical.

Is the data collection request for default-on or default-off?

Default on for all channels.

Does the instrumentation include the addition of any new identifiers?


Is the data collection covered by the existing Firefox privacy notice?


Does the data collection use a third-party collection tool?


Result: datareview+

Attachment #9235591 - Flags: data-review?(chutten) → data-review+
Pushed by
Remove child interception telemetries related codes. r=dom-worker-reviewers,asuth
Adding telemetry for spawning service worker. r=dom-worker-reviewers,asuth
Adding telemetry for evaluating whole fetch interception duration. r=dom-worker-reviewers,asuth
Adding telemetry for evaluating the duration of fetch event dispatching and response synthesizing. r=dom-worker-reviewers,asuth
You need to log in before you can comment on or make changes to this bug.