Intent to Prototype: CPU Performance API

33 views
Skip to first unread message

Nikos Papaspyrou

unread,
9:38 AM (5 hours ago) 9:38 AM
to blin...@chromium.org, Michael Lippautz, Dominic Farolino
Contact emails
niko...@chromium.org

Explainer
https://github.com/explainers-by-googlers/cpu-performance

Specification
None

Summary
Expose some information about how powerful the user device is. This API targets web applications that will use this information to provide an improved user experience, possibly in combination with the Compute Pressure API, which provides information about the user device’s CPU pressure/utilization and allows applications to react to changes in CPU pressure.

Blink component
Blink>PerformanceAPIs

Web Feature ID
Missing feature

Motivation
At present, some video conferencing applications support advanced functionality by relying on internal/private browser extensions or APIs to classify devices into performance categories. Our proposal allows these applications to support existing functionality without depending on such non-standard features. Applications whose functionality depends on client-side hardware detection often resort to running benchmark workloads, to estimate hardware capabilities. Providing a public CPU Performance API would help prevent a needless waste of resources.

Initial public proposal
https://github.com/explainers-by-googlers/cpu-performance

TAG review
None

TAG review status
Pending

Risks


Interoperability and Compatibility
None

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None


Debuggability
None

Is this feature fully tested by web-platform-tests?
Yes. However, testing this feature will inevitably be limited. Tests cannot assert that a particular hardware combination will yield a particular integer value, and are restricted to non-undefined-ness and non-zero-ness.


Requires code in //chrome?
True

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

Estimated milestones

Intent to ship roughly by the end of 2025, in M145.



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

This intent message was generated by Chrome Platform Status.

--
Nikos Papaspyrou <niko...@google.com>

Jeffrey Yasskin

unread,
10:08 AM (4 hours ago) 10:08 AM
to Nikos Papaspyrou, blink-dev, Michael Lippautz, Dominic Farolino


On Wed, Oct 8, 2025, 6:38 AM 'Nikos Papaspyrou' via blink-dev <blin...@chromium.org> wrote:
Contact emails
niko...@chromium.org

Explainer
https://github.com/explainers-by-googlers/cpu-performance

Specification
None

Summary
Expose some information about how powerful the user device is. This API targets web applications that will use this information to provide an improved user experience, possibly in combination with the Compute Pressure API, which provides information about the user device’s CPU pressure/utilization and allows applications to react to changes in CPU pressure.

Blink component
Blink>PerformanceAPIs

Web Feature ID
Missing feature

Motivation
At present, some video conferencing applications support advanced functionality by relying on internal/private browser extensions or APIs to classify devices into performance categories. Our proposal allows these applications to support existing functionality without depending on such non-standard features. Applications whose functionality depends on client-side hardware detection often resort to running benchmark workloads, to estimate hardware capabilities. Providing a public CPU Performance API would help prevent a needless waste of resources.

Initial public proposal
https://github.com/explainers-by-googlers/cpu-performance

TAG review
None

TAG review status
Pending


From a TAG perspective, it will probably avoid a round trip if you can present this to the Privacy WG before sending the TAG review. 

Thanks, 
Jeffrey

--
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/CAMHN%3DHydj6Q7pz6i_y3j1ON20a270NFGx%2BKD11Q3VdfTXvtCDg%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages