It appears some values where we divide by the measurement interval are warping the results (like spikes of >1Mbps readings on audio bandwidth, likely due to an 'interval' that's very short, and several packets came in). We should smooth to (say) 1 second of measurements, and store until we get >= 1s (for example), or at least throw away too-short interval results.
Created attachment 8640037 [details] MozReview Request: Bug 1188441: treat assertion failures as bad mozconfig; r?mshal Bug 1188441: treat assertion failures as bad mozconfig; r?mshal
Sorry, bug # typo
backlog: --- → webRTC+
Priority: -- → P1
Assignee: nobody → rjesup
Rank: 19 → 22
Priority: P1 → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.