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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggK65vwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg__LfrgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_9aC9QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_8PMtQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_8f6vwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_93GpgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgv6_BpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_8LJ5AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_9_itgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg__fKnQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_4_RrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggOGjuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_8qw9AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggLCpqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_4qS4QgM


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release

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

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

Suspected Commit
  Author : dtapuska
  Commit : 5494d50ab65532c64a28e91e23b0a722ebbfe8ed
  Date   : Wed Jan 04 22:02:35 2017
  Subject: Remove the requirement to only rAF align non-blocking touch moves.

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : first_gesture_scroll_update_latency/Docs  (1 open document tab)
  Change       : 142.08% | 11.5167142857 -> 27.8801428571

Revision             Result                  N
chromium@441469      11.5167 +- 49.0358      14      good
chromium@441476      5.03067 +- 1.48411      9       good
chromium@441477      16.1514 +- 92.3507      9       good
chromium@441478      31.67 +- 55.9318        9       bad       <--
chromium@441479      26.9398 +- 29.1483      6       bad
chromium@441482      23.0319 +- 21.5191      14      bad
chromium@441495      27.8801 +- 50.3757      14      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=Docs...1.open.document.tab. smoothness.top_25_smooth

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

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


| 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 Tests>AutoBisect.  Thank you!