Open
Bug 1188441
Opened 9 years ago
Updated 2 years ago
Scrub webrtc telemetry values that generate out-of-range results due to small delta times
Categories
(Core :: WebRTC, defect, P3)
Core
WebRTC
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox42 | --- | affected |
| backlog | webrtc/webaudio+ |
People
(Reporter: jesup, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
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.
|
||
Comment 1•9 years ago
|
||
Bug 1188441: treat assertion failures as bad mozconfig; r?mshal
Attachment #8640037 -
Flags: review?(mshal)
|
|
||
Updated•9 years ago
|
Attachment #8640037 -
Attachment is obsolete: true
Attachment #8640037 -
Flags: review?(mshal)
|
|
||
Comment 2•9 years ago
|
||
Sorry, bug # typo
|
Reporter | |
Updated•9 years ago
|
Depends on: webrtc-telemetry
|
|
Reporter | |
Updated•9 years ago
|
backlog: --- → webRTC+
Rank: 19
Priority: -- → P1
|
||
Updated•9 years ago
|
Assignee: nobody → rjesup
Rank: 19 → 22
Priority: P1 → P2
|
||
Comment 3•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
|
||
Updated•3 years ago
|
Blocks: webrtc-telemetry
No longer depends on: webrtc-telemetry
|
|
Reporter | |
Updated•2 years ago
|
Assignee: rjesup → nobody
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•