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

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


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

chromium-rel-win7-x64-dual

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : media.desktop
  Metric       : cpu_time_percentage_avg/video.html?src_crowd1080_vp9.webm

Revision             Result                     N
chromium@512445      0.143766 +- 0.0325189      21      good
chromium@512468      0.142733 +- 0.0248446      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.crowd1080.vp9.webm media.desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8964195534518294208


For feedback, file a bug with component Speed>Bisection