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

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


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : frame_times/http___nytimes.com_

Revision             Result                  N
chromium@526446      16.9594 +- 1.78868      21      good
chromium@526459      16.9784 +- 1.7796       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...nytimes.com. smoothness.sync_scroll.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/8957695255589608304


For feedback, file a bug with component Speed>Bisection

This appears to be just a revert of a recent improvement.