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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/Pinterest

Revision             Result                  N
chromium@464673      7.34948 +- 1.8212       21      good
chromium@464691      7.37448 +- 1.01073      21      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=Pinterest smoothness.key_mobile_sites_smooth

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970301906538319584


For feedback, file a bug with component Speed>Bisection

Looks like this benchmark was down for 4 months and regressed when it came up again. Just on this device, so likely had a device swap. Not much we can do here, range is too big to bisect.