[compute-pressure] Analytics / RUM use cases? (#233)

nicjansma has just created a new issue for https://github.com/w3c/compute-pressure:

== Analytics / RUM use cases? ==
Hi!

I was wondering if there was consideration for using this API for measuring and segmenting the performance of browsing sessions, e.g. via Real User Monitoring (RUM) tools.

For example, I could see the compute pressures of fair/serious/critical being an important signal for segmenting user experiences during scenarios like Page Load, or in-page SPA Soft Navigations.  It's likely those buckets will see degraded browsing performance, and users of RUM could slide/dice/filter by the Compute Pressure to better understand good and bad experiences.

When reviewing and testing out the current `PressureObserver` API, one thing that would be useful would be to be able to gather "buffered" entries that have happened prior to requesting.  This is a pattern we use in `PerformanceObserver` for RUM when those RUM tools load "late" in the page-load process, so they can "look back" and get details back in history.

https://w3c.github.io/performance-timeline/#performanceobserverinit-dictionary

Without buffered entries, when RUM tools initialize, if they start a `PressureObserver` they can't know the "current" (or past) state of compute pressure for that browsing session, until the pressure state changes.

Would a `buffered` flag be compatible with the goals and privacy/security concerns of this API?

Side question, was there any discussion of just using the `PerformanceObserver` API directly?

Thanks!

Please view or discuss this issue at https://github.com/w3c/compute-pressure/issues/233 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 16 September 2023 14:40:53 UTC