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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : css_animation:power_avg/load_search/load_search_amazon

Revision             Result                    N
chromium@484421      0.911076 +- 0.435315      12      good
chromium@484780      0.939898 +- 0.28954       15      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.amazon 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/8973652066182630400


For feedback, file a bug with component Speed>Bisection