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

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


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

android-nexus5

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

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

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


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : ulan
  Commit : 5a766b4401b262aa7dcf9e32e37157ddb8a07b28
  Date   : Tue May 02 14:28:11 2017
  Subject: [heap] Fix computation of marking progress in incremental finalization.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-incremental-finalize_sum/browse_chrome/browse_chrome_newtab
  Change       : 79.48% | 7.3945 -> 13.2718333333

Revision                           Result                  N
chromium@468925                    7.3945 +- 1.2773        6       good
chromium@468950                    7.98533 +- 1.6177       6       good
chromium@468963                    7.7085 +- 2.63852       6       good
chromium@468969                    7.31133 +- 1.46894      6       good
chromium@468972                    7.22067 +- 2.89606      9       good
chromium@468973                    7.62771 +- 3.55503      14      good
chromium@468973,v8@0d582ada51      7.53667 +- 1.46198      6       good
chromium@468973,v8@8d628bc920      7.5585 +- 2.35005       6       good
chromium@468973,v8@5a766b4401      12.687 +- 2.02856       6       bad       <--
chromium@468973,v8@63a40cae7c      12.8462 +- 2.82596      6       bad
chromium@468973,v8@94ca3b6809      11.9669 +- 17.7682      21      bad
chromium@468974                    12.7143 +- 13.5548      14      bad
chromium@468975                    13.2718 +- 2.98854      6       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.chrome.newtab v8.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980400391808575520

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5814685930094592


| 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 Speed>Bisection.  Thank you!

The CL is changing GC timing