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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : load:energy_sum/browse_tech/browse_tech_discourse_infinite_scroll

Revision             Result                  N
chromium@490905      34.9936 +- 8.37996      21      good
chromium@491376      35.1199 +- 11.62        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=browse.tech.discourse.infinite.scroll 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/8972190859312955328


For feedback, file a bug with component Speed>Bisection

Ref builds regressed, so wontfix.