Skip to main content

Why are the WebRTC statistics in watchRTC different than what I see in webrtc-internals?

The watchRTC SDK works similarly to webrtc-internals, but collects at slightly different time intervals.

webrtc-internals can collect at a frequency of a second. For most of our watchRTC clients, we configure the collection frequency of the SDK to 8 seconds or more. We are trying to keep a delicate balance here: on one hand, we want to get as much data and at a lower frequency, on the other hand we don’t want our collection to take up too much CPU or network resources.

Since watchRTC usually collects its metrics at frequencies of over a second, it misses some of the granularity that webrtc-internals can achieve, averaging out metrics a bit more.

Was this article helpful?

0 out of 0 found this helpful