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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5bvkpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxdXG5wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpY2UjAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5cH9swkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5ZKXpgsM


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

android-nexus5

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

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


===== SUSPECTED CL(s) =====
Subject : [heap] New heuristics for incremental marking step size.
Author  : ulan
Commit description:
  
This patch simplifies code for speeding up marking and
removes write barrier counter.

The step size is now computed based in two parts:
- bytes to mark in order to keep up with allocation,
- bytes to mark in order to make progress.

BUG= chromium:616434 ,  chromium:646139 , chromium:644819
LOG=NO

Review-Url: https://codereview.chromium.org/2359903002
Cr-Commit-Position: refs/heads/master@{#39827}
Commit  : 1beb89f24cb01663843a7519921e7caf0910c760
Date    : Wed Sep 28 13:27:59 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@421571                2569812  156466   5  good
chromium@421597                2597907  159365   5  good
chromium@421610                2664723  179583   5  good
chromium@421617                2741671  80906.6  5  good
chromium@421619                2503844  47265.3  5  good
chromium@421619,v8@24ae2955ec  2611760  203857   5  good
chromium@421619,v8@0698f10661  2534495  159022   5  good
chromium@421619,v8@4c2fd5cd5f  2682885  139644   5  good
chromium@421619,v8@1beb89f24c  3519338  186350   5  bad    <--
chromium@421619,v8@669719d5fb  3551209  110468   5  bad
chromium@421620                3621342  161549   5  bad
chromium@421623                3551929  136758   5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 653803

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg
Relative Change: 38.22%
Score: 99.9

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


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

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