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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : scroll_response:energy_sum/browse_social/browse_social_twitter

Revision             Result                    N
chromium@484258      0.444085 +- 0.210736      21      good
chromium@484421      0.424718 +- 0.120546      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.social.twitter 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/8974256497426192672


For feedback, file a bug with component Speed>Bisection

Tracking with ref build