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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnsLP8woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnunD-ggM


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

android-nexus6
chromium-rel-win7-gpu-nvidia

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

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

Hi tzik@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 : tzik
  Commit : 211d6bc6aacfeed4aa730418801c86c7cef6719c
  Date   : Thu Jun 29 04:19:13 2017
  Subject: Notify RendererScheduler of starting LOADING phase on DidStartProvisionalLoad

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-incremental-step_sum/browse_media/browse_media_facebook_photos
  Change       : 88.59% | 153.949333333 -> 290.3365

Revision             Result                  N
chromium@483279      153.949 +- 59.5214      6      good
chromium@483292      181.475 +- 72.0237      6      good
chromium@483294      154.043 +- 136.638      6      good
chromium@483295      286.571 +- 64.7138      5      bad       <--
chromium@483298      290.973 +- 54.932       6      bad
chromium@483304      290.336 +- 22.3897      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.media.facebook.photos v8.runtimestats.browsing_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8975102135384849648


For feedback, file a bug with component Speed>Bisection

v8-gc-full-mark-compactor_sum value was decreased at the same time, and the sum of them looks unchanged. My change probably cause a V8 GC mode change?
https://chromeperf.appspot.com/report?sid=8a59ac273759f2418d5bd5a717a1dd84bc37d6baa8172ca4a3f1cb75b2267d53&start_rev=480277&end_rev=483917&rev=483304

Adding mlippautz for double check.

If you look at the x axis you notice that there's quite some data missing. We had commits inbetween that could've changed the baseline here.

There's nothing to be done for this CL. Thanks for checking back.

Actually, jgruber@ pointed out offline that the graphs I was mentioning are assigned to other bugs. 

The graphs assigned to this bug show that runtime just switches buckets. This is still a WontFix.

 Issue 739308  has been merged into this issue.

Issue 738817 has been merged into this issue.

 Issue 739307  has been merged into this issue.

 Issue 739307  has been merged into this issue.

 Issue 739747  has been merged into this issue.

Issue 739321 has been merged into this issue.