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

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


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

win-high-dpi

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

=== 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/browse_news/browse_news_nytimes

Revision             Result                  N
chromium@491729      16.2916 +- 3.23782      21      good
chromium@491809      16.0544 +- 4.70648      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.news.nytimes 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/8971643988344021312


For feedback, file a bug with component Speed>Bisection

The refs move in parallel.