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

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


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

android-nexus5X

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

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

Hi ulan@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] Decouple old generation allocation limit from external memory. (patchset #1 id:1 of https://codereview.chromium.org/2329993002/ )
Author  : ulan
Commit description:
  
Reason for revert:
Regressions in telemetry benchmarks:
 crbug.com/646819 .

Original issue's description:
> [heap] Decouple old generation allocation limit from external memory.
>
> We check for external memory limit in Heap::ReportExternalMemoryPressure.
>
> BUG= chromium:616434 
>
> Committed: https://crrev.com/672d079ccba686019fa1457c83b42c2e692ef88b
> Cr-Commit-Position: refs/heads/master@{#39374}

TBR=hpayer@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= chromium:616434 

Review-Url: https://codereview.chromium.org/2339033005
Cr-Commit-Position: refs/heads/master@{#39442}
Commit  : eeb4f28aed721c343d43be6e454fafba4c0f7ea6
Date    : Thu Sep 15 10:14:22 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@418876                66565.6  1539.2   5  good
chromium@418890                66917.0  1739.84  8  good
chromium@418890,v8@f84f45f9ca  67332.0  1772.71  5  good
chromium@418890,v8@eeb4f28aed  77469.6  1619.98  5  bad    <--
chromium@418890,v8@b37daacd6b  76907.2  1517.2   5  bad
chromium@418890,v8@b848716c98  77029.6  1177.21  5  bad
chromium@418891                76289.6  1806.89  5  bad
chromium@418892                77805.0  1856.27  4  bad
chromium@418894                77256.8  2711.0   5  bad
chromium@418897                73583.5  6060.49  8  bad
chromium@418904                76233.0  1018.9   8  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 647609

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests indexeddb_perf
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 13.75%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/675
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001372012720897824


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

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

The suspect CL is a revert.