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

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


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

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

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

=== 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_shopping/browse_shopping_avito
  Change       : 9.98% | 6775542.0 -> 7451704.0

Revision                                                     Result                  N
android-chrome@99b6fd7dae                                    6775542 +- 36879.3      6      good
android-chrome@6d62ea7763                                    6812755 +- 87570.2      6      good
android-chrome@e5eafcf94f                                    6596447 +- 478768       6      good
android-chrome@74662f91c8                                    6815323 +- 182812       6      good
android-chrome@74662f91c8,chromium@575926                    6881504 +- 129065       9      good
android-chrome@74662f91c8,chromium@575929                    6829452 +- 137000       9      good
android-chrome@74662f91c8,chromium@575929,v8@46a78fbedf      7401936 +- 478543       9      bad       <--
android-chrome@74662f91c8,chromium@575929,v8@e3a5b1e402      7462040 +- 350140       9      bad
android-chrome@74662f91c8,chromium@575929,v8@16af1baac4      7469813 +- 184588       6      bad
android-chrome@74662f91c8,chromium@575930                    7618812 +- 86803.4      6      bad
android-chrome@74662f91c8,chromium@575931                    7441493 +- 505024       9      bad
android-chrome@74662f91c8,chromium@575935                    7574109 +- 242092       6      bad
android-chrome@1032e70048                                    7870315 +- 241870       6      bad
android-chrome@478583399d                                    7637577 +- 409470       6      bad
android-chrome@029430f630                                    7451704 +- 225263       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.shopping.avito 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/8940499277737272176


For feedback, file a bug with component Speed>Bisection

 Issue 865869  has been merged into this issue.