- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Feb 2025 14:08:56 +0000
- To: public-webrtc-logs@w3.org
If I understand correctly, the concern of overhead is in the browser doing an expensive calculation most websites would never request (though per-frame is not an issue due to caching, per-second might be; is _never_ an acceptable frequency?)
How expensive is this computation? Our webstats model is like a boat we keep loading with new stuff. Eventually, it becomes problematic.
At some point (maybe now?) might we wish we had something like this?
```js
await sender.getStats({verbosity: "high"}) // low | medium (default) | high
```
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/794#issuecomment-2688072345 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 February 2025 14:08:57 UTC