New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 839746 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.5%-13.4% regression in webrtc_perf_tests at 23033:23041

Project Member Reported by philipel@chromium.org, May 4 2018

Issue description

Changes caused by https://webrtc.googlesource.com/src/+/a12bdbfe6e9cb271dd744c3e2c7267915e048a35

What part of that roll that caused the actual regressions is a bit unclear, but I can see there are changes to ffmpeg. Do we use ffmpeg for anything VP9 related? If so I think that is our best bet.

Dale, could you please take a look?
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=839746

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=fe6e08e1dc0ae969a7578fbc6c88a422b2d381deca65f8d3bf5183e3b82ee80e


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

webrtc-linux-large-tests
webrtc-mac-large-tests
webrtc-win-large-tests
Cc: oprypin@chromium.org
Components: Blink>WebRTC>Video
Owner: ----
Status: Available (was: Assigned)
Note (and sorry about this) the ffmpeg revision range in the commit message is incorrect.
By looking at the diff of the DEPS file, there are only 
2 ffmpeg commits in the range:
https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+log/c6aed052ab..3eebd979 
and they are much less suspicious than some others that could potentially be included.

Sign in to add a comment