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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : load:energy_sum/load_news/load_news_flipboard

Revision             Result                  N
chromium@491613      12.5816 +- 6.49261      21      good
chromium@491729      11.917 +- 4.47997       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.news.flipboard 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/8971847543269552944


For feedback, file a bug with component Speed>Bisection

Ref also moves.