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

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


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

android-one

Kicked off another bisect:
https://chromeperf.appspot.com/buildbucket_job_status/9013034954034642784

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


===== SUSPECTED CL(s) =====
Subject : Reland of "[heap] Uncommit pooled pages concurrently"
Author  : mlippautz
Commit description:
  
- Move the concurrent unmapping to MemoryAllocator
- Hide (private) members where possible
- MemoryAllocator:Free is now the bottleneck for freeing
- Pooled pages are either allocated from a set of pooled pages are obtained
  through work stealing from the concurrent unmapper

BUG= chromium:605866 , chromium:581412
LOG=N

This reverts commit 25ff296c4c8d35c63255531a86f877f20eeaeb62.

Review-Url: https://codereview.chromium.org/1929503002
Cr-Commit-Position: refs/heads/master@{#35910}
Commit  : 45f52fcb60f75bfe5dc5f6a83317a14db631cf18
Date    : Fri Apr 29 14:28:18 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev    N  Good?
chromium@389402                2.9062   0.0222056  5  good
chromium@390620                2.8261   0.0273679  5  good
chromium@390697                2.8405   0.0498076  8  good
chromium@390700                2.87843  0.092372   8  good
chromium@390700,v8@45f52fcb60  3.12722  0.0370862  8  bad    <--
chromium@390700,v8@b83edcc8b1  3.16635  0.0441815  5  bad
chromium@390701                3.17111  0.116071   8  bad
chromium@390702                3.13593  0.0224831  5  bad
chromium@390707                3.1771   0.0450906  5  bad
chromium@390716                3.19566  0.117113   5  bad
chromium@390735                3.13633  0.0226768  5  bad
chromium@390773                3.11645  0.0276585  5  bad
chromium@390925                3.12589  0.0270994  5  bad
chromium@391229                3.13595  0.0415644  5  bad
chromium@391837                3.17603  0.0445014  5  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 609120

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: tasks_per_second_total_all/css-animation.html
Relative Change: 9.28%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/649
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013034954034642784


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

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