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

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


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

android-nexus5

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

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

Suspected Commit
  Author : David Bokan
  Commit : 771bc4ee1d609083dd81daa0ee78229b49dfa270
  Date   : Thu Oct 05 18:39:46 2017
  Subject: Use viewport coords in gpuBenchmarking gestures

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.top_25_smooth
  Metric       : mean_input_event_latency/https___www.google.com__hl_en_q_barack+obama
  Change       : 27.16% | 14.6303333333 -> 18.604

Revision             Result                  N
chromium@506756      14.6303 +- 2.51246      6      good
chromium@506796      14.6437 +- 1.64814      6      good
chromium@506801      14.8813 +- 2.79847      6      good
chromium@506803      15.2837 +- 2.16638      6      good
chromium@506804      18.5997 +- 1.59818      6      bad       <--
chromium@506806      17.6823 +- 2.49467      6      bad
chromium@506816      17.6832 +- 1.68933      6      bad
chromium@506835      18.604 +- 1.3739        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=https...www.google.com..hl.en.q.barack.obama smoothness.gpu_rasterization.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection