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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : video_animation:power_avg/video.html?src_garden2_10s.mp4

Revision             Result                  N
chromium@492252      5.52952 +- 2.1129       21      good
chromium@492254      5.40032 +- 1.63746      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.garden2.10s.mp4 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/8970675627576726304


For feedback, file a bug with component Speed>Bisection