Closed Bug 986513 Opened 11 years ago Closed 5 years ago

Adjust resolution and framerate algorithm for load/bitrate adaptation

Categories

(Core :: WebRTC: Audio/Video, defect, P3)

Product:
Core
Component:
WebRTC: Audio/Video
Version:
Other Branch
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: jesup, Assigned: jesup)

References

Details

(Whiteboard: [p=8])

The default google algorithm has issues; adjustment and/or (partial) replacement makes sense. gcp has identified some instabilities in the result ("porpoising") in certain situations. Exactly how much improvement is needed is something that we need to investigate in real-world tests (and some dummynet/etc tests) There needs to be a fair bit of hysteresis in the algorithm. You can see also my other bug on this with a simple proposed algorithm for adapting by bitrate (see https://bugzilla.mozilla.org/attachment.cgi?id=756806).
Blocks: 970725
backlog: --- → Fx32+
Whiteboard: [p=10, ft:webrtc, priority]
Target Milestone: --- → mozilla32
Priority: -- → P1
Whiteboard: [p=10, ft:webrtc, priority] → [p=10, ft:webrtc, priority][s=fx32]
Whiteboard: [p=10, ft:webrtc, priority][s=fx32] → [p=8, est:8d, priority][s=fx32]
Summary: Adjust resolution and framerate algorithm for load/bitrate adaption → Adjust resolution and framerate algorithm for load/bitrate adaptation
Depends on: 1007775
QA Contact: drno
No longer blocks: 970426
Whiteboard: [p=8, est:8d, priority][s=fx32] → [p=8, est:8d, priority][s=fx33]
Target Milestone: mozilla32 → mozilla33
backlog: Fx32+ → -
Whiteboard: [p=8, est:8d, priority][s=fx33] → [p=8, est:8d, priority]
backlog: - → ---
Whiteboard: [p=8, est:8d, priority] → [p=8]
Depends on: 1027100
Bumping this to Fx 34 given other priorities
Target Milestone: mozilla33 → mozilla34
Priority: P1 → P2
backlog: --- → webRTC+
Rank: 25
Also look to merge in encode-time measurements of load used by Chrome.
Assignee: pkerr → rjesup
Rank: 25 → 15
Priority: P2 → P1
Target Milestone: mozilla34 → ---
Depends on: 1306940
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3

Since all the depending bugs have been closed and I believe we do have load adaptions I think we can consider this done. If it's not working as expected we should open a new bug.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.