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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : idle:power_avg/video.html?src_crowd2160.mp4

Revision             Result                   N
chromium@487022      11.3311 +- 0.878253      21      good
chromium@487029      11.4309 +- 1.46431       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.crowd2160.mp4 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/8973437792807719072


For feedback, file a bug with component Speed>Bisection

bisect can't repro.