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

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


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

win-high-dpi

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

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

Revision             Result                   N
chromium@484182      6.71047 +- 1.705         21      good
chromium@484258      6.65389 +- 0.915005      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.ogg.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/8974706171567725008


For feedback, file a bug with component Speed>Bisection