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

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


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

win-zenbook

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

=== Auto-CCing suspected CL author v8-autoroll@chromium.org ===

Hi v8-autoroll@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 : Update V8 to version 5.5.108.
Author  : v8-autoroll
Commit description:
  
Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/1b154e42..a3f63e16

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,littledan@chromium.org,vogelheim@chromium.org

Review-Url: https://codereview.chromium.org/2315913002
Cr-Commit-Position: refs/heads/master@{#416743}
Commit  : beca90bba41c1ab10075ea0789f386d7009b6aa1
Date    : Tue Sep 06 23:00:31 2016


===== TESTED REVISIONS =====
Revision                       Mean    Std Dev  N   Good?
chromium@416705                227006  19922.9  5   good
chromium@416732                226551  56530.1  8   good
chromium@416739                237731  74491.0  5   good
chromium@416741                218428  6888.47  5   good
chromium@416742                219838  7038.21  5   good
chromium@416742,v8@11f74547f8  298609  90135.0  18  good
chromium@416742,v8@a3f63e163b  358422  82184.1  18  good
chromium@416743                406603  17261.4  12  bad    <--
chromium@416746                364774  38638.4  8   bad
chromium@416759                376021  5679.72  5   bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 645373

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests webrtc.datachannel
Test Metric: vm_working_set_final_size_total/vm_working_set_final_size_total
Relative Change: 65.64%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/470
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002017730004077392


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

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

I'm pretty sure this is actually caused by chromium@416742,v8@a3f63e163b
Restarted a bisect to verify.

===== 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@416705                211494  17858.9  18  good
chromium@416732                218299  23954.6  62  good
chromium@416739                215833  30747.9  62  good
chromium@416741                229457  38992.5  12  good
chromium@416742                225674  28886.6  41  good
chromium@416742,v8@7bc200c767  222892  35142.3  27  good
chromium@416742,v8@4b618dbf8e  321850  98481.5  41  bad    <--
chromium@416742,v8@11f74547f8  337935  101707   27  bad
chromium@416743                355381  77821.8  12  bad
chromium@416746                298039  101829   62  bad
chromium@416759                203569  5355.58  18  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 645373

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests webrtc.datachannel
Test Metric: vm_working_set_final_size_total/vm_working_set_final_size_total
Relative Change: 1.08%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/533
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999526621449220416


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

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