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

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


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

android-one

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

=== 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:
  
Decrease regular heap object size to 400k. In a follow up, we can now get rid of
the new space border page while keeping the 1M minimum new space size.

This reverts commit 1617043c1093870d67eede7828467cc3b77ba9fb.

BUG= chromium:636331 

Review-Url: https://codereview.chromium.org/2278653003
Cr-Commit-Position: refs/heads/master@{#38916}
Commit  : 2101e691caeef656eb91f1c98620b3955d337c83
Date    : Thu Aug 25 16:26:32 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev     N  Good?
chromium@414882                0.354594  0.00217931  5  good
chromium@414889                0.354604  0.00236528  5  good
chromium@414892                0.355287  0.0021513   5  good
chromium@414893                0.354928  0.00225136  5  good
chromium@414893,v8@6e67d04260  0.35543   0.00135878  5  good
chromium@414893,v8@2646749cbc  0.358291  0.00284554  5  good
chromium@414893,v8@58cac6501f  0.357803  0.00370441  5  good
chromium@414893,v8@2101e691ca  0.411069  0.00287216  5  bad    <--
chromium@414893,v8@f93ca29cac  0.411189  0.00196519  5  bad
chromium@414893,v8@4c5c0d83e4  0.41292   0.00255065  5  bad
chromium@414894                0.412535  0.00279528  5  bad
chromium@414895                0.409978  0.0017811   5  bad
chromium@414908                0.409943  0.00135042  5  bad
chromium@414933                0.409705  0.00339359  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 642119

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: thread_total_all_cpu_time_per_second/css-animation.html
Relative Change: 15.54%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1585
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002962201765901664


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

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

CL has already been reverted.