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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzK3iugsM


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

chromium-rel-mac-retina

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 1c2910f5ef29e52e1d4f5bc139e8515d8bcf1a85
  bad_revision : 5a7f45dab8372cb7b80ee24dfb137a7ced2049ea

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : scroll_response:energy_sum/browse_search/browse_search_google

Revision             Result                  N
chromium@458826      193.111 +- 6.75587      6      good
chromium@458899      192.504 +- 2.13539      6      good
chromium@458918      210.696 +- 63.4758      6      good
chromium@458921      303.718 +- 64.816       6      bad
chromium@458923      300.117 +- 77.0615      6      bad
chromium@458927      316.963 +- 62.2054      6      bad
chromium@458936      299.142 +- 4.26318      5      bad
chromium@458972      318.363 +- 71.8921      6      bad
chromium@459118      298.864 +- 7.65307      6      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=browse.search.google system_health.common_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983870630864698240

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5876287777800192


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : chongz
  Commit : 5a7f45dab8372cb7b80ee24dfb137a7ced2049ea
  Date   : Wed Mar 22 23:13:14 2017
  Subject: Enable VsyncAlignedInput to field trial

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : scroll_response:energy_sum/browse_search/browse_search_google
  Change       : 49.53% | 117.072842132 -> 175.053883296

Revision             Result                  N
chromium@458918      117.073 +- 31.1363      6      good
chromium@458920      122.912 +- 42.5625      6      good
chromium@458921      175.054 +- 1.85341      6      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=browse.search.google system_health.common_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983780356312085504

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5854378176544768


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

This graph shows (https://chromeperf.appspot.com/report?sid=d76b179d58246e5445250545b20628d4548b438872f9c2f1a400646455d38882) that this has a negligible impact on actual scroll power, but impacts the total energy consumed by scroll responses because it just makes those responses last longer. It's possible this means that it just doesn't make sense to report scroll response energy.