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

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


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

android-nexus5X

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

=== 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 : [heap] Do more incremental marking work in tasks.
Author  : ulan
Commit description:
  
This patch changes incremental marking work scheduling from combination
of idle/delayed tasks to ordinary short-running tasks and moves
more marking work from V8.Execute to tasks by accounting how much
bytes were marked in tasks.

BUG= chromium:616434 
LOG=NO

Review-Url: https://codereview.chromium.org/2321553002
Cr-Commit-Position: refs/heads/master@{#39348}
Commit  : 6a1b49d79c610cc981ec35598a8a070951f8c3f7
Date    : Mon Sep 12 11:46:30 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@417973                5745409  47387.2  5  good
chromium@417981                5743245  134578   8  good
chromium@417986                5733184  206370   8  good
chromium@417987                5720182  230986   5  good
chromium@417987,v8@8ffbd333bb  5750213  90115.4  5  good
chromium@417987,v8@6a1b49d79c  6200133  211063   5  bad    <--
chromium@417987,v8@4cf5ee6b38  6391687  237161   5  bad
chromium@417988                6296507  220049   8  bad
chromium@417990                6386682  205504   5  bad
chromium@418006                6597897  172719   5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 646826

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:effective_size_avg
Relative Change: 14.84%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/672
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001540615715908528


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

| 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 CL changes GC timing. The total heap size is unaffected, so closing.