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

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


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

chromium-rel-win7-dual

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

=== 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 : Revert of [heap] Remove border page
Author  : mlippautz
Commit description:
  
Reason for revert:
No real improvement as we still lack the ability to promote from
scavenges/young gen GCs.

Let's keep this in mind for later.

Original issue's description:
> [heap] Remove border page
>
> A page now belongs either the nursery *or* the intermediate gen. The page that
> contained objects of both spaces is removed in this change.
>
> BUG= chromium:636331 
>
> Committed: https://crrev.com/42ece47446f0dbd3779d6e0e00dce97a1931a9f9
> Cr-Commit-Position: refs/heads/master@{#39778}

TBR=ulan@chromium.org,hpayer@chromium.org
BUG= chromium:636331 

Review-Url: https://codereview.chromium.org/2383443002
Cr-Commit-Position: refs/heads/master@{#39854}
Commit  : 9af3142fbadfe99e53c378dbe6e363e17aed89af
Date    : Thu Sep 29 09:21:08 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev    N   Good?
chromium@421856                0.917859  0.050509   18  good
chromium@421856,v8@1e937f6676  0.912155  0.0446491  5   good
chromium@421856,v8@9af3142fba  0.98145   0.0592241  18  bad    <--
chromium@421856,v8@964f54ba1a  1.00896   0.0756875  12  bad
chromium@421857                1.0042    0.0986969  12  bad
chromium@421858                1.01849   0.0532536  8   bad
chromium@421860                1.03982   0.0469854  8   bad
chromium@421863                1.00523   0.0473649  5   bad
chromium@421870                1.04627   0.083447   8   bad
chromium@421883                1.02778   0.0558527  8   bad
chromium@421910                1.02899   0.0349337  8   bad

Bisect job ran on: win_perf_bisect
Bug ID: 652302

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_tbmv2
Test Metric: v8-gc-total_avg/v8-gc-total_avg
Relative Change: 9.03%
Score: 99.8

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6966
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999809228027588656


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

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

Unfortunately this is intended. Removing the border page would tank some microbenchmarks so we cannot land it (yet).