W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2019

Re: [webrtc-stats] Detecting glitches (#443)

From: ilnik via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Jun 2019 07:50:52 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-501160914-1560325851-sysbot+gh@w3.org>
The old metric returns the max for 1 second window. It's designed, so that application polling getStats every second would notice any glitches. It can be alternatively changed to be a maximum inter-frame delay since the last GetStats call.

No other aggregation than max can help to identify such glitches: after a 100ms glitch, next frames would be decoded and sent for render almost immediately. So average inter-frame delay for the second with the glitch would stay the same. Fps wouldn't be affected either.

GitHub Notification of comment by ilyanikolaevskiy
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/443#issuecomment-501160914 using your GitHub account
Received on Wednesday, 12 June 2019 07:50:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 12 June 2019 07:50:55 UTC