anssiko
commented
11 months ago Thank you for this proposal and use case description. I have triaged this use case as https://github.com/w3c/compute-pressure/labels/V2 and it will discussed with the group.
DenizUgur
I have read the specification and some of the issues if this has been discussed before and closest I've found is issue #24.
Apperantly it has been decided to not expose low level metrics and show higher level of CPU utilization via "pressure" abstraction. Which I agree that this is a good way to move forwards and many use cases would prefer this.
I have a niche use case, which might be worth considering. I believe that exposing low level metrics such as current CPU, GPU, memory utilization per page would be fantastic for side-by-side comparison of some feature.
A great example for this could be comparing two different implementations of a video player on separate windows. In this case one might better compared to another by 5% but we wouldn't know that with the current "state" abstraction.
There are many ways to achieve this in controlled environments, such as a webserver relaying the system metrics or via a chrome extension? For the sake of completeness of this specification, I propose to add low-level metrics either as a raw value or average of different periods. This could be permission restricted or maybe only allowed through chrome flags.
What are your thoughts on this?