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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : css_animation:power_avg/video.html?src_garden2_10s.webm

Revision             Result                  N
chromium@491729      13.1346 +- 1.97578      21      good
chromium@491809      12.8887 +- 1.5319       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/8971770151805302464


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:browser_process:reported_by_chrome:tracing:effective_size_avg/video.html?src_crowd1080.webm
  Change       : 0.62% | 67067097.1429 -> 67485650.2857

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/692fd67b7eb1b5ad6f816c9f2068a76df622ef52..d54c0c1eccbddf90ea69bd14ca1290d721eee9b9


Revision             Result                   N
chromium@490303      67067097 +- 1102371      14       good
chromium@491177      67114197 +- 577237       14       good
chromium@491617      67168075 +- 1029516      21       good
chromium@491833      67136535 +- 1530494      21       good
chromium@491847      67030689 +- 526523       9        good
chromium@491854      67070021 +- 841900       9        good
chromium@491857      66990333 +- 1503536      14       good
chromium@491858      67000957 +- 412513       6        good
chromium@491859      ---                      ---      build failure
chromium@491860      67459705 +- 1046885      14       bad
chromium@491887      67430855 +- 1536152      21       bad
chromium@491941      67521793 +- 1099020      14       bad
chromium@492049      67485650 +- 1206389      14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.crowd1080.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/8971174620548537984


For feedback, file a bug with component Speed>Bisection

Bisect isn't reproing a 20% increase in power, looks like noise.