Currently, it is difficult for web developers to understand how their applications perform in the wide variety of conditions encountered on real user devices. A native self-profiling API for JS code would also allow web developers to efficiently find hotspots in their JS code during page loads and user interactions, to assign CPU budgets to individual JS-implemented features on the page, to find unnecessary work being done on the client, and to find low-priority JS code executing in the background and wasting device power.
Specification being incubated in a Community Group
Status in Chromium
Enabled by default
Consensus & Standardization
Intent to Prototype urlIntent to Prototype thread
Search tagsprofiler, profiling, js,
Last updated on 2021-10-17