Issue 640181 link

Starred by 2 users

Issue metadata

Status:	Fixed
Owner:	█ philipel@chromium.org Last visit > 30 days ago
Closed:	Oct 2016
Cc:	peah@chromium.org
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	2
Type:	Bug-Regression
M-54

19.3%-338.5% regression in webrtc_perf_tests at 13757:13760

Project Member Reported by hlundin@chromium.org, Aug 23 2016

Issue description

Blame range: https://chromium.googlesource.com/external/webrtc/+log/f96c51ac057ec8e2cace58c5ecdfecce65a03a6d..4a1ec1e639b0e78ca1f189b19205782c4b9ab0af

4a1ec1e Added ProbeBitrate(bitrate_bps, num_probes) to BitrateProber. by philipel · 8 days ago
1aee0b5 Remove old methods in AudioTransport, make it pass a gn build by maxmorin · 8 days ago
c8c71f4 Revert of Move FilePlayer and FileRecorder to Voice Engine (patchset #6 id:100001 of https://codereview.webrtc.org/2240163002/ ) by kwiberg · 8 days ago
dc65ea2 Move FilePlayer and FileRecorder to Voice Engine by kwiberg · 8 days ago

Comment 1 by hlundin@chromium.org, Aug 23 2016

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzsrNsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzvqQpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjvvttgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzvKWqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzvLxuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzt2iuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzsHMuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzvLtpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjt_SrQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzt22pgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzsagswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzvK7twoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjv6vpAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzt71pwoM


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

webrtc-android-tests-nexus5
webrtc-android-tests-nexus72
webrtc-android-tests-nexus9

Comment 2 by hlundin@chromium.org, Aug 23 2016

Labels: -M-52 M-54
Owner: philipel@chromium.org

philipel: your CL looks like the most suspicious one.

Comment 3 by hlundin@chromium.org, Aug 23 2016

Cc: peah@chromium.org

Comment 4 by philipel@google.com, Aug 23 2016

I haven't looked through all the graphs but I'm pretty certain most of the changes are due to my CL.

The reason for the change is that earlier we probed at x3 and x6 the initial start bitrate, but here we probe at 900 kbps and 1800 kbps regardless of the inital start bitrate.

This CL should undo the changes to these metrics:
https://codereview.webrtc.org/2269993002/

Comment 5 by peah@chromium.org, Oct 21 2016

Any updates on this? Can this be closed?

Comment 6 by philipel@chromium.org, Oct 21 2016

Status: Fixed (was: Assigned)

This has been fixed, closing.

►

Issue 640181 link

Issue metadata

19.3%-338.5% regression in webrtc_perf_tests at 13757:13760

Issue description

Comment 1 by hlundin@chromium.org, Aug 23 2016

Comment 1 Deleted

Comment 2 by hlundin@chromium.org, Aug 23 2016

Comment 2 Deleted

Comment 3 by hlundin@chromium.org, Aug 23 2016

Comment 3 Deleted

Comment 4 by philipel@google.com, Aug 23 2016

Comment 4 Deleted

Comment 5 by peah@chromium.org, Oct 21 2016

Comment 5 Deleted

Comment 6 by philipel@chromium.org, Oct 21 2016

Comment 6 Deleted

Sign in to add a comment