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

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


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

win-high-dpi

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

=== 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_social/load_social_pinterest

Revision             Result                  N
chromium@484152      38.3972 +- 6.40073      21      good
chromium@484258      38.9317 +- 12.1832      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.social.pinterest 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/8974257380108382576


For feedback, file a bug with component Speed>Bisection

Not a real regression, ref builds also moved