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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.desktop
  Metric       : story:power_avg/video.html?src_tulip2.vp9.webm_background

Revision             Result                  N
chromium@512003      8.22758 +- 4.60182      21      good
chromium@512106      7.79392 +- 2.51334      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.tulip2.vp9.webm.background media.desktop

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

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


For feedback, file a bug with component Speed>Bisection

no bisect, closing as WontFix.