Adds a web-exposed sampling profiler for measuring client JavaScript execution time. Gathering JS profiles from real users can help developers debug slow observed performance without the need for invasive manual instrumentation.

Motivation

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.

Demo

• https://wicg.github.io/js-self-profiling/#examples

Documentation

• https://docs.google.com/document/d/1NGrU6xVWHq8uLfSFRfDWh1v_UiXLiOgr2FDb2KIaoL0/edit?usp=sharing
• https://docs.google.com/document/d/1OTwlBnAMXZEaOICtuz16c01QnkPPdqHBoHpfGwnk5SY/edit?usp=sharing

Specification

Specification link

Status: Specification being incubated in a Community Group

Status in Chromium

Blink components: Blink>PerformanceAPIs

Implementation status: Enabled by default (tracking bug)

Consensus & Standardization

• Firefox: No signal
• Edge: Positive
• Safari: Negative
• Web Developers: Strongly positive

Owners

• acomminos@fb.com
• tdresser@chromium.org
• npm@chromium.org

Intent to Prototype url

Search tags

Last updated on 2021-10-16