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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxfKApgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpeT-uAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxfrbrAsM


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

chromium-rel-win7-gpu-nvidia

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000055934044516544

=== Auto-CCing suspected CL author zmo@chromium.org ===

Hi zmo@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Enable ANGLE ES3 by default in Chromium (Windows)
Author  : zmo
Commit description:
  
We can use --disable-es3-angle or driver bug workaround list to turn
it off if it's problematic on certain platforms.

BUG= 649101 
TEST=win bots
R=piman@chromium.org,kbr@chromium.org,geofflang@chromium.org
NOTRY=true
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2354423002
Cr-Commit-Position: refs/heads/master@{#420802}
Commit  : d78d37f99d13ec5eef3570badd4959c36e367342
Date    : Sat Sep 24 00:56:43 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@420690  109.966  3.03512  5  good
chromium@420746  112.548  8.46577  5  good
chromium@420774  110.938  11.9434  5  good
chromium@420788  115.07   3.13208  5  good
chromium@420795  115.914  1.6152   5  good
chromium@420799  112.825  17.6121  5  good
chromium@420801  112.939  5.19039  5  good
chromium@420802  210.905  17.1352  5  bad    <--

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 651978

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests media.tough_video_cases_extra
Test Metric: seek/video.html?src_tulip2.mp4
Relative Change: 91.79%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1891
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000055934044516544


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5824651886854144

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Geoff, can you take a look?

Haven't been able to reproduce yet.  According to the bots, only this one .mp4 test regressed and only on NVIDIA.

Does your build contain the proprietary video codecs? These are the GN args needed:

ffmpeg_branding="Chrome"
proprietary_codecs=true

Comes from src/tools/mb/mb_config.pyl, the "chrome_with_codecs" mixin.

This regression has been included in a stable release and that stable channel is now deprecated. I'm closing this so that we won't have unresponsive performance regressions in the future.