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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : after_load:power_avg/load_games/load_games_miniclip

Revision             Result                   N
chromium@484152      7.50879 +- 0.584076      21      good
chromium@484258      7.63035 +- 1.82164       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=load.games.miniclip system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Ref build also moved, not a real regression