Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682)

Thank you for the response. Just to not lose context here - is there multiple stakeholder interest for this?

> External processes are out of scope, the goal is to help developers understand how their own application behave in the wild.
> This include hotspots and unecessary code execution wasting the user's CPU cycles.

What about workers? The main concern was about the main thread profile data missing context about high compute pressure, caused either by a worker or an external process. It would be useful if there was a way to share some context when main thread is not getting enough CPU time, as the perf timings for those scenarios would be very different.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/682#issuecomment-1088473250
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/682/1088473250@github.com>