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

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


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

win-high-dpi

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

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

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

Revision             Result                  N
chromium@486358      11.3726 +- 1.13972      21      good
chromium@486459      11.5441 +- 1.65628      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.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/8973799167649247232


For feedback, file a bug with component Speed>Bisection

bisect can't repro, I think this is due to noise.