Intent to Prototype: Compute Pressure
Olivier Yiptong
Contact emails
oyip...@chromium.org, pwn...@chromium.orgExplainer
https://github.com/oyiptong/compute-pressure/blob/main/README.md
Specification
NoneSummary
Gives the ability for web applications to anticipate and react to computational load changes on a device. Today, no API exists to provide signals about system computation usage. This API also gives a signal about processor state with respect to speed throttling.
Blink component
Blink>PerformanceAPIs>ComputePressureMotivation
Web applications are today being used to provide a wide range of solutions, including some use-cases that push the capabilities of the device they are running on, e.g. video gaming and video-conferencing. It is a testament to the web's power as a platform that one application will run on devices ranging from low-powered devices all the way to the most powerful machines. However, a one-size-fits all approach does not work well for computational intensive applications; a missing capability of the web is to allow developers to tailor the experience depending on computational capacity. Compute-intensive web apps that want to provide a good experience across their user base rely on browser extensions to access system metrics. The Compute Pressure API will let developers write web applications that anticipate and react to system load changes to provide a great experience for users regardless of their device's compute prowess.
Initial public proposal
https://github.com/WICG/proposals/issues/28TAG review
NoneTAG review status
PendingRisks
Interoperability and Compatibility
None
Gecko: No signal
WebKit: No signal
Web developers: No signals