- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Jan 2022 20:32:37 +0000
- To: public-webrtc-logs@w3.org
You get ten experience points for asking a great question. Check your level. https://w3c.github.io/webrtc-stats/#dom-rtcicecandidatepairstats-bytessent is defined as *not* including STUN checks which would be in the order of ~100 per second. RTCP is the obvious culprit. The fiddle makes it hard to see though since there is an active track drowning everything else. Did you check with a stopped track? Wireshark should give you a good number (including SRTCP overhead) -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/613#issuecomment-1013454644 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 January 2022 20:32:38 UTC