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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg55_CpAkM


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

android-nexus5

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

=== PERF REGRESSION ===


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

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


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


===== SUSPECTED CL(s) =====
Subject : Revert "[heap] Use RAIL mode for initial heap sizing"
Author  : ulan
Commit description:
  
This reverts commit aea4f1a704829fcb3fc3584b9d9948deeb5bcaa5.

Reason: performance regression on benchmarks (crbug.com/671118).

BUG=chromium:671118, chromium:613518 
TBR=hpayer@chromium.org

Review-Url: https://codereview.chromium.org/2549053002
Cr-Commit-Position: refs/heads/master@{#41479}
Commit  : a1680631ff09a6082538fd8887bab00e0bdb3383
Date    : Mon Dec 05 10:15:21 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev  N   Good?
chromium@436245                33885962  966285   8   good
chromium@436264                34013422  2078647  12  good
chromium@436269                34138255  2822427  18  good
chromium@436272                33839134  813190   8   good
chromium@436272,v8@a97258b00c  33688720  0.0      5   good
chromium@436272,v8@a1680631ff  34556176  1507944  5   bad    <--
chromium@436272,v8@f295aa2af5  35656098  1950757  5   bad
chromium@436273                35315796  2703155  8   bad
chromium@436274                34766815  2709882  12  bad
chromium@436283                35263685  1568047  5   bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 672087

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=browse.news.qq system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_news/browse_news_qq
Relative Change: 4.07%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4418
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993921198066502512


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

| 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!

Closing since the regression is caused by a revert.

Good to know that my original CL improved the memory usage.