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

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


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

android-nexus6

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

=== Auto-CCing suspected CL author dtapuska@chromium.org ===

Hi dtapuska@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : dtapuska
  Commit : abf462cdff2f095ab1ab69beb78c8b658bfb634a
  Date   : Fri Mar 03 03:46:57 2017
  Subject: Disable the passthrough touch event queue for now.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : frame_times/http___www.androidpolice.com_2012_10_03_rumor-evidence-mounts-that-an-lg-optimus-g-nexus-is-coming-along-with-a-nexus-phone-certification-program_
  Change       : 50.65% | 18.5630362576 -> 27.9644925508

Revision             Result                   N
chromium@454412      18.563 +- 0.978902       6      good
chromium@454460      18.5838 +- 1.13077       6      good
chromium@454484      18.4608 +- 0.550128      6      good
chromium@454496      18.6893 +- 0.967327      6      good
chromium@454502      18.787 +- 1.59827        6      good
chromium@454503      18.6 +- 1.09485          6      good
chromium@454504      27.9823 +- 0.858186      6      bad       <--
chromium@454505      28.3813 +- 1.44694       6      bad
chromium@454507      27.9645 +- 0.985258      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.androidpolice.com.2012.10.03.rumor.evidence.mounts.that.an.lg.optimus.g.nexus.is.coming.along.with.a.nexus.phone.certification.program. smoothness.sync_scroll.key_mobile_sites_smooth

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

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


| 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!

If you look at the graph it is consistent before the initial change landed and after the revert of the original change. The graph in the middle was due to the change not behaving correctly for acking the touchmoves.