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

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


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

win-high-dpi

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

=== 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_tulip2.vp9.webm_seek

Revision             Result                  N
chromium@494708      9.61788 +- 1.63818      21      good
chromium@494898      9.58635 +- 1.19412      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.tulip2.vp9.webm.seek 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/8970458522556847424


For feedback, file a bug with component Speed>Bisection