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

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


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

win-high-dpi

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

=== 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.mp3_type_audio

Revision             Result                     N
chromium@512003      0.376015 +- 0.0657862      21      good
chromium@512106      0.381035 +- 0.103227       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.mp3.type.audio media.desktop

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

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


For feedback, file a bug with component Speed>Bisection

no bisect, closing as WontFix.