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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : story:power_avg/video.html?src_tulip2.wav_type_audio

Revision             Result                    N
chromium@485150      0.553764 +- 0.128233      21      good
chromium@485162      0.558498 +- 0.14475       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.wav.type.audio 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/8973895487348222624


For feedback, file a bug with component Speed>Bisection