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

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


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

chromium-rel-mac11
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : video_animation:power_avg/video.html?src_crowd720_vp9.webm

Revision             Result                  N
chromium@494018      10.3112 +- 1.02169      21      good
chromium@494047      10.3992 +- 1.99298      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.crowd720.vp9.webm media.tough_video_cases_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection