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

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


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

win-high-dpi

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

=== 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.webm

Revision             Result                   N
chromium@491729      11.2051 +- 0.636105      21      good
chromium@491809      11.2493 +- 1.05688       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.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/8971895466109431888


For feedback, file a bug with component Speed>Bisection

Bisect didn't find a culprit, and now the regression is stale.