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

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


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

android-nexus5

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

=== 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 : Reland "[heap] Start sweeper tasks after evacuation. (patchset #2 id:20001 of https://chromiumcodereview.appspot.com/2428043002/ )"
Author  : ulan
Commit description:
  
The performance regression in crbug.com/657776 was not caused by this CL.

This reverts commit 4490a7601c81647a4fb93da94360f271eb172473.

BUG=

Review-Url: https://chromiumcodereview.appspot.com/2437873004
Cr-Commit-Position: refs/heads/master@{#40478}
Commit  : 189794ddb289029b224be64cd0dddb3487fae371
Date    : Thu Oct 20 16:25:26 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev    N  Good?
chromium@426566                5.11448  0.0463258  5  good
chromium@426600                5.11307  0.0565639  5  good
chromium@426609                5.1041   0.0533112  5  good
chromium@426610                5.09975  0.0560695  8  good
chromium@426610,v8@5331e3b616  5.07431  0.044648   5  good
chromium@426610,v8@189794ddb2  5.23042  0.0525232  8  bad    <--
chromium@426611                5.25276  0.0545991  5  bad
chromium@426613                5.27442  0.0269676  5  bad
chromium@426617                5.23262  0.0220857  5  bad
chromium@426634                5.29353  0.0352892  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 659062

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: tasks_per_second_total_all/set-timeout.html
Relative Change: 3.50%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4280
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997836094294102896


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

| 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 change utilizes more tasks to finish GC earlier. So regression in tasks_per_second_total_all is expected.