New issue
Advanced search Search tips

Issue 707746 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

30.8%-36.2% regression in webrtc_perf_tests at 17491:17491

Project Member Reported by ilnik@chromium.org, Apr 3 2017

Issue description

Please check that these changes are expected.
The reland of your commit also caused the same regressions:
https://chromium.googlesource.com/external/webrtc/+/76d9c9c3826f3c3622d3e8869fa54f7b39e70427
 

Comment 1 by ilnik@chromium.org, Apr 3 2017

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=707746

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnP_WqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3LKq8AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3OaXqgsM


Bot(s) for this bug's original alert(s):

webrtc-android-tests-nexus5-kitkat
webrtc-mac-large-tests
Cc: terelius@chromium.org
Status: WontFix (was: Assigned)
Thanks Ilya, this is somewhat expected I think, so I'll close this.

We probably want to try to improve this in the future, but it's a trade off and here we've basically decided to aim at more stable BWE at the expense of higher latency.

Sign in to add a comment