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

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


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

android-webview-nexus6

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

=== 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_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_browser_cpu_time_per_frame/http___cuteoverload.com
  Change       : 32.28% | 2.84163356277 -> 3.75887292657

Revision             Result                    N
chromium@506783      2.84163 +- 0.0880144      6      good
chromium@506801      2.8304 +- 0.0751395       6      good
chromium@506803      2.84245 +- 0.113944       6      good
chromium@506804      3.72222 +- 0.0509479      6      bad       <--
chromium@506806      3.73105 +- 0.0728597      6      bad
chromium@506810      3.74333 +- 0.149614       6      bad
chromium@506819      3.71097 +- 0.0639195      6      bad
chromium@506854      3.75887 +- 0.0991033      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...cuteoverload.com thread_times.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/8966459529433038752


For feedback, file a bug with component Speed>Bisection