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

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


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

perf-go-phone-1024

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

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

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_yandex
  Change       : 0.19% | 4035781.71429 -> 4027920.7619

Revision                       Result                  N
android-chrome@4426288b2b      4035782 +- 59109.3      21      good
android-chrome@dda312c828      4027921 +- 57348.4      21      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.yandex system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection