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

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


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

linux-release

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N   Good?
chromium@433542  149.76  17.3528  50  good
chromium@433559  149.68  14.2436  50  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 670766

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests sunspider
Test Metric: Total/Total
Relative Change: 0.05%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6875
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994365124490113424


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

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

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

=== PERF REGRESSION ===


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

Hi verwaest@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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


===== SUSPECTED CL(s) =====
Subject : [zone] Fix zone segment pooling size limits
Author  : verwaest
Commit description:
  
BUG= chromium:655129 

Review-Url: https://codereview.chromium.org/2520903002
Cr-Commit-Position: refs/heads/master@{#41138}
Commit  : 4097c8503e4c033713e4b07ee01072896cbfd381
Date    : Mon Nov 21 13:22:29 2016


===== TESTED REVISIONS =====
Revision                       Mean    Std Dev  N   Good?
chromium@433442                149.28  16.127   50  good
chromium@433551                149.68  15.4557  50  good
chromium@433605                150.72  30.1675  50  good
chromium@433606                149.8   19.3391  50  good
chromium@433606,v8@4513532f63  148.18  14.8115  50  good
chromium@433606,v8@8ca50a8862  148.22  16.9287  50  good
chromium@433606,v8@2405ab11b5  148.64  17.0153  50  good
chromium@433606,v8@4097c8503e  152.04  19.5939  50  bad    <--
chromium@433607                153.28  22.1829  50  bad
chromium@433609                153.58  20.6441  50  bad
chromium@433612                153.1   18.8282  50  bad
chromium@433619                154.18  18.2587  50  bad
chromium@433632                152.04  15.4894  50  bad
chromium@433659                152.38  16.1177  50  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 670766

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests sunspider
Test Metric: Total/Total
Relative Change: 2.08%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6881
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994121172461772496


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

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

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