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

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


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

win-high-dpi

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

=== 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_crowd1080_vp9.webm

Revision             Result                   N
chromium@512003      11.0591 +- 0.511282      21      good
chromium@512106      11.1149 +- 0.426263      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/8964198550464738832


For feedback, file a bug with component Speed>Bisection

no bisect, closing as WontFix.