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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqz6tQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tyY4QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-pfhtwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tzm6QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghui48QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tzm6QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-ofC8AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-qP6rQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-umPuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-s7e6goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-qOrsgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghsnL5wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgut-LpQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghurytQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-snQkQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghvKQowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghrLiuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-t-GgwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuDT8AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-uqStwsM


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

android-nexus5X
android-nexus6
android-webview-nexus5X

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : sigbjornf
  Commit : ec3056b0028de68485f6e5c4b6d57f225d334605
  Date   : Fri May 26 08:24:26 2017
  Subject: Enable heap compaction on all 'container' arenas.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_chrome/load_chrome_blank
  Change       : 3.73% | 16891330.6667 -> 17521773.3333

Revision             Result                   N
chromium@474934      16891331 +- 118303       6      good
chromium@474952      16926317 +- 55303.9      6      good
chromium@474961      16936045 +- 84821.2      6      good
chromium@474965      16931608 +- 164370       6      good
chromium@474966      17525528 +- 46679.1      6      bad       <--
chromium@474967      17530989 +- 74205.3      6      bad
chromium@474969      17521773 +- 138469       6      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.chrome.blank system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8978200371884486816

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5903779381116928


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!