2 - Sampling strategy coupling between backend (server) and frontend (client)There is no way to defer profiling overhead to a non-critical period (e.g., after page load).There is no way to incur overhead only if the Profiling API is actually used. Many users are unwilling to trade page load performance for profiling capabilities.
(See https://github.com/WICG/js-self-profiling/issues/86 for full context)To avoid overhead on unsampled sessions, sampling must be aligned between server and client, which introduces operational complexity.In many setups, sampling occurs on the client side; keeping server and client in sync requires additional tooling. Even if a session is not sampled, the presence of the header means the page still pays the warm-up cost.
No milestones specified