- From: Varun Singh via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Jun 2019 13:48:40 +0000
- To: public-webrtc-logs@w3.org
bursts metrics are the best way to do something like this. Define a minimum time threshold that would invoke the counter, total duration metric that would count up all freeze durations, and a max frozen duration which would be the maximum observed freeze duration. typically, I would do something like: ``` non_max_duration = total_freeze_duration - max_frozen_duration avg_non_max = non_max_duration/freeze_count // if avg_non_max is much lower to max_frozen, then max_frozen was an anomaly ``` -- GitHub Notification of comment by vr000m Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/443#issuecomment-502116239 using your GitHub account
Received on Friday, 14 June 2019 13:48:41 UTC