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

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


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_GPU_cpu_time_per_frame/http___jsfiddle.net_xLuvC_1_show_

Revision             Result                  N
chromium@511112      26.1517 +- 1.95281      21      good
chromium@511161      26.6454 +- 8.3171       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...jsfiddle.net.xLuvC.1.show. thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection

These timeseries have recovered and changed modality since October.