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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_raster_cpu_time_per_frame/http___cuteoverload.com

Revision             Result                    N
chromium@518229      2.67252 +- 0.0684562      21      good
chromium@518240      2.67432 +- 0.0653554      21      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/8962039313344316944


For feedback, file a bug with component Speed>Bisection

This looks to be within the noise.