Intent to Prototype: js-profiling in dedicated workers

8 views
Skip to first unread message

Chromestatus

unread,
1:11 PM (6 hours ago) 1:11 PM
to blin...@chromium.org, moni...@microsoft.com
Contact emails
moni...@microsoft.com

Explainer
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DocumentPolicy/DocumentPolicyInWorkers.md

Specification
https://github.com/WICG/js-self-profiling/pull/88

Summary
Allows js-profiling in dedicated workers This feature enables the JavaScript Self‑Profiling (js-profiling) API in Dedicated Workers, while remaining gated by Document Policy. It allows developers to obtain low‑overhead CPU attribution for JavaScript execution in workers, with Document Policy support for workers tracked separately.

Blink component
Blink>PerformanceAPIs

Web Feature ID
profiler

Motivation
Modern web applications increasingly offload performance‑critical work to Dedicated Workers to keep the main thread responsive. While the JavaScript Self‑Profiling API provides low‑overhead CPU attribution for JavaScript execution, it is currently unavailable in workers due to its reliance on Document Policy, leaving developers without visibility into where CPU time is spent during background computation. Enabling js-profiling in Dedicated Workers fills this gap by allowing developers to capture representative JavaScript CPU profiles for worker execution, using the same explicit opt‑in and policy‑gated model already required for documents.

Initial public proposal
https://github.com/WICG/js-self-profiling/issues/33

Requires code in //chrome?
False

Tracking bug
https://issues.chromium.org/issues/482085416

Estimated milestones

No milestones specified



Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5159559872249856?gate=5181493867577344

This intent message was generated by Chrome Platform Status.

Michal Mocny

unread,
1:28 PM (5 hours ago) 1:28 PM
to Chromestatus, blin...@chromium.org, moni...@microsoft.com
Neat!  Just a heads up that there is another active prototype in this area right now.  (And perhaps you would also be interested in helping review some of that work?)

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69975252.050a0220.1f729.0da6.GAE%40google.com.
Reply all
Reply to author
Forward
0 new messages