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

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


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

health-plan-webview-low-end-phone

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

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

Bisect Details
  Configuration: webview-low-end-phone-perf-bisect
  Benchmark    : system_health.webview_startup
  Metric       : webview_startup_wall_time_avg/load_chrome/load_chrome_blank
  Change       : 4.58% | 672.405333334 -> 641.578571429

Revision                       Result                  N
android-chrome@a03058257f      672.405 +- 287.966      21      good
android-chrome@120ca38372      641.579 +- 212.451      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=load.chrome.blank system_health.webview_startup

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

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


For feedback, file a bug with component Speed>Bisection