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

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


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

health-plan-clankium-low-end-phone
health-plan-webview-low-end-phone
perf-go-phone-512

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

=== Auto-CCing suspected CL author sigurds@chromium.org ===

Hi sigurds@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Sigurd Schneider
  Commit : 46a78fbedfcd458f5d35097bdf1a9947644f4b0e
  Date   : Tue Jul 17 15:33:20 2018
  Subject: Revert "[embedded-builtins] Enable on all arches except x86 for benchmarks"

Bisect Details
  Configuration: go-phone-512-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_reddit
  Change       : 6.24% | 8654649.33333 -> 9194930.0

Revision                                                     Result                  N
android-chrome@99b6fd7dae                                    8654649 +- 226523       6      good
android-chrome@6d62ea7763                                    8621749 +- 191908       6      good
android-chrome@e5eafcf94f                                    8674474 +- 164976       9      good
android-chrome@74662f91c8                                    8734797 +- 292306       9      good
android-chrome@74662f91c8,chromium@575926                    8474643 +- 162970       6      good
android-chrome@74662f91c8,chromium@575929                    8574596 +- 216659       6      good
android-chrome@74662f91c8,chromium@575929,v8@46a78fbedf      9231902 +- 160434       6      bad       <--
android-chrome@74662f91c8,chromium@575929,v8@e3a5b1e402      9098793 +- 13644.9      6      bad
android-chrome@74662f91c8,chromium@575929,v8@16af1baac4      9121389 +- 63019.8      6      bad
android-chrome@74662f91c8,chromium@575930                    9148629 +- 80583.8      6      bad
android-chrome@74662f91c8,chromium@575931                    9196625 +- 191781       6      bad
android-chrome@74662f91c8,chromium@575935                    9302213 +- 256210       6      bad
android-chrome@1032e70048                                    9109020 +- 55260.8      9      bad
android-chrome@478583399d                                    9120939 +- 42632.4      6      bad
android-chrome@029430f630                                    9194930 +- 224949       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit 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/8940223068355647088


For feedback, file a bug with component Speed>Bisection