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

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


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

win-high-dpi

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

=== 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_search/load_search_baidu

Revision             Result                   N
chromium@484152      1.09293 +- 0.721799      21      good
chromium@484258      1.13171 +- 0.709313      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.search.baidu 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/8974260971228305536


For feedback, file a bug with component Speed>Bisection

Ref builds moved, not a real regression