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

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


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

android-nexus7v2

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@416493  37460.9  168.033  9   good
chromium@416715  37617.7  191.434  12  good
chromium@416729  37890.4  129.695  5   bad
chromium@416743  37875.3  188.551  12  bad
chromium@416771  37867.7  158.111  12  bad
chromium@416826  37914.7  209.937  12  bad
chromium@416937  37912.0  261.576  12  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 645372

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests webrtc.peerconnection
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 1.64%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3299
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002017791330654048


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

| 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/9001926243110458432

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@416493  37460.9  168.033  9   good
chromium@416715  37617.7  191.434  12  good
chromium@416729  37890.4  129.695  5   bad
chromium@416743  37875.3  188.551  12  bad
chromium@416771  37867.7  158.111  12  bad
chromium@416826  37914.7  209.937  12  bad
chromium@416937  37912.0  261.576  12  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 645372

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests webrtc.peerconnection
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 1.64%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3299
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002017791330654048


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

| 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/9001834773783527136

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

Hi mlippautz@chromium.org, 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 : [heap] Switch to 500k pages
Author  : mlippautz
Commit description:
  
BUG= chromium:636331 
R=ulan@chromium.org

Review-Url: https://codereview.chromium.org/2314803002
Cr-Commit-Position: refs/heads/master@{#39220}
Commit  : 4b618dbf8ec7f0edf377b54b48bf3c852d5e235a
Date    : Tue Sep 06 17:55:36 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N   Good?
chromium@416493                37544.0  206.601  9   good
chromium@416715                37667.3  260.336  27  good
chromium@416729                37731.8  268.076  41  good
chromium@416736                37781.3  243.87   41  good
chromium@416740                37736.4  290.884  27  good
chromium@416742                37748.3  239.995  27  good
chromium@416742,v8@7bc200c767  37703.7  216.563  27  good
chromium@416742,v8@4b618dbf8e  37893.1  148.434  18  bad    <--
chromium@416742,v8@11f74547f8  37924.0  204.776  18  bad
chromium@416743                37887.0  185.021  41  bad
chromium@416771                37913.1  214.964  18  bad
chromium@416826                37964.9  116.696  18  bad
chromium@416937                38010.7  186.523  12  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 645372

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests webrtc.peerconnection
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 1.42%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3303
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002017791330654048


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

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

Ping mlippautz@. Do you expect your CL to cause this regression?

Possibly. WontFix, as the CL significantly improves memory consumption on small pages, see issue 644677.