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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : css_animation:power_avg/video.html?src_crowd1080_vp9.webm

Revision             Result                 N
chromium@493392      9.80791 +- 3.5456      21      good
chromium@493533      10.0629 +- 2.8111      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=video.html.src.crowd1080.vp9.webm media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8971084451458680320


For feedback, file a bug with component Speed>Bisection

WontFix=ing because alerts were turned off for this metric due to noise and it doesn't repro in bisect.