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

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


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

android-nexus5X

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@416713  5.44175  1.08534    5  good
chromium@416716  6.03525  0.292698   5  good
chromium@416717  2.28376  0.142099   5  bad
chromium@416718  2.04557  0.2528     5  bad
chromium@416723  2.09857  0.250323   5  bad
chromium@416732  2.2573   0.0843168  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 651486

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.mobile_infinite_scroll_tbmv2
Test Metric: v8-gc-incremental-step_max/v8-gc-incremental-step_max
Relative Change: 58.52%
Score: 0

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


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

| 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/9000090929219237888

+robertocn: r416718 is a v8 roll. Why didn't bisect descend into v8?

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@416713  5.66831  0.385131  5  good
chromium@416716  5.56285  0.813379  5  good
chromium@416717  2.18725  0.134218  5  bad
chromium@416718  2.118    0.168029  5  bad
chromium@416723  2.24355  0.177448  5  bad
chromium@416732  2.22675  0.127197  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 651486

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.mobile_infinite_scroll_tbmv2
Test Metric: v8-gc-incremental-step_max/v8-gc-incremental-step_max
Relative Change: 60.72%
Score: 0

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


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

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

This issue is about performance improvement. I wanted to verify that improvement comes from V8 roll.