- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Nov 2022 09:19:40 +0000
- To: public-webrtc-logs@w3.org
Because the CPU% is a system-wide metric I think we should add a new stats dictionary, e.g. RTCSystemStats, and we could guard the exposure of that entire object on the HW exposure criterion. The alternative would be to add it to RTCPeerConnectionStats simply because that is a singleton that always exists. > Hardware encoders/decoders may also queue frames internally, so abnormally high encode/decode times may be reported even in situations where performance is not degraded. Agree it's just a heuristic and sometimes it is wrong. This issue is about adding actual system information, not proxy info! -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/710#issuecomment-1331856958 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 November 2022 09:19:41 UTC