WebRTC BWE is a bit too sensitive in M50. |
|||||||
Issue description<b>Version: <Kenneth, what is the frequency?></b> <b>OS: <please tell me it's not XP></b> What steps will reproduce the problem? Run a WebRTC call (apprtc demo) in loopback on a mobile device, such as Galaxy S5. At times it can be seen that the BWE doesn't ramp up as expected. What is the expected output? What do you see instead? BWE can get stuck at low bitrates. Instead it should be able to ramp up to 2 Mbps. Please use labels and text to provide additional information.
,
Mar 14 2016
,
Mar 14 2016
,
Mar 14 2016
Should the WebRTC fix mentioned in #2 be merged into M50? If so, what kind of sanity checks should we run with Canary Chrome before requesting a merge?
,
Mar 14 2016
Yes, that's the plan. I haven't been able to reliably reproduce the issue with Chrome, but for sanity I think it would be good to just verify that the BWE seems to be working. We could run a test with netem and bandwidth limited to 1 Mbps and see that it looks OK.
,
Mar 14 2016
,
Mar 15 2016
Your change meets the bar and is auto-approved for M50 (branch: 2661)
,
Mar 15 2016
I ran some tests with netem and verified that webrtc still adapted to the bandwidth limitation.
,
Mar 15 2016
Merge done: https://chromium.googlesource.com/external/webrtc/+/55d15f82f68f8f4daece1000e8641b45898b8b9a
,
Mar 15 2016
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by holmer@chromium.org
, Mar 14 2016