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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_azeqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_azFugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_fvUtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_eGctQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvaeVtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_YOIqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_Za2pAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_ayTpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_ZbJtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_YqIuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_ZbdrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_bu7uQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_Za2pAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvcenoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_YrspQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_eGGrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_ajyoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_ayPtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_db0swoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_dbqqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_eH1ogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_ajusAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvb_YoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_eHhvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_YPsuQoM


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

android-nexus6

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@426610  5885000  74879.7  5  good
chromium@426618  6549393  62984.4  5  bad
chromium@426625  6536278  84703.3  5  bad
chromium@426640  6580250  77874.5  5  bad
chromium@426669  6593335  61835.6  5  bad
chromium@426727  6650096  175412   5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 660154

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_hackernews
Relative Change: 13.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2697
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997615379438416320


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5834547441172480

| 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 Tests>AutoBisect.  Thank you!

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

=== Auto-CCing suspected CL author heimbuef@google.com ===

Hi heimbuef@google.com, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Constrain the zone segment pool size
Author  : heimbuef
Commit description:
  
Added a size constraint to the configuration to limit the segment pool.
This will likely fix the memory alerts from small android devices.

BUG= chromium:655129 

Review-Url: https://chromiumcodereview.appspot.com/2424393002
Cr-Commit-Position: refs/heads/master@{#40476}
Commit  : ef690ca387c116569a2f5dbd71c6f0733a070cc6
Date    : Thu Oct 20 14:48:55 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@426610                6568338  29324.7  5  good
chromium@426610,v8@ef690ca387  7318878  19232.4  5  bad    <--
chromium@426610,v8@5331e3b616  7322905  8797.07  5  bad
chromium@426610,v8@189794ddb2  7268540  19375.4  5  bad
chromium@426611                7289582  21995.7  5  bad
chromium@426612                7262322  10951.6  5  bad
chromium@426614                7257014  25211.9  5  bad
chromium@426618                7272435  38062.8  5  bad
chromium@426625                7251428  24101.2  5  bad
chromium@426640                7284580  43173.9  5  bad
chromium@426669                7264906  15489.7  5  bad
chromium@426727                7273338  22341.8  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 660154

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.stackoverflow system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_tools/load_tools_stackoverflow
Relative Change: 10.73%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2700
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997523803353910576


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5003436104351744

| 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 Tests>AutoBisect.  Thank you!

This owner is not able to receive e-mails, please re-triage.

Stale, and metrics have improved a ton since this regression.