New issue
Advanced search Search tips

Issue 738835 link

Starred by 1 user
Status: WontFix
Owner:
tzik@chromium.org
Closed: Jul 2017
Cc:
jgruber@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

191.2% regression in v8.runtimestats.browsing_mobile at 483037:483182

Project Member Reported by jgruber@chromium.org, Jul 3 2017 
See the link to graphs below.

Comment 1 by jgruber@chromium.org, Jul 3 2017 

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

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 3 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_facebook_photos

Revision             Result                  N
chromium@483036      16.1039 +- 28.5726      17      good
chromium@483182      18.2477 +- 34.7906      21      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/8975102076809198016


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jul 3 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_facebook_photos

Revision             Result                  N
chromium@483036      15.8532 +- 34.2518      16      good
chromium@483182      18.3691 +- 31.5727      17      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/8975090291222182176


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jul 4 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_facebook_photos

Revision             Result                  N
chromium@482982      16.1049 +- 35.0907      19      good
chromium@483182      15.3097 +- 28.8263      15      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/8975021192773617200


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jul 4 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_facebook_photos

Revision             Result                  N
chromium@482982      21.4368 +- 45.6752      20      good
chromium@483182      21.9871 +- 32.2202      18      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/8975011017756547056


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Jul 7 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_facebook_photos

Revision             Result                  N
chromium@482982      14.6395 +- 27.731       17      good
chromium@483182      18.4628 +- 34.9458      16      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/8974748627669115424


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Jul 10 2017

Cc: scottmg@chromium.org
Owner: scottmg@chromium.org

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

Hi scottmg@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 : Scott Graham
  Commit : 72146922f21b8ba39bbb829f3caa97af21e50f57
  Date   : Thu Jun 29 04:29:54 2017
  Subject: fuchsia: fix break after https://chromium-review.googlesource.com/c/553979/

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_facebook_photos
  Change       : 110.89% | 15.764 -> 37.7591111111

Revision             Result                  N
chromium@483036      15.764 +- 23.901        9       good
chromium@483194      19.0185 +- 37.4619      13      good
chromium@483273      16.1882 +- 20.196       5       good
chromium@483293      15.6724 +- 20.0854      5       good
chromium@483295      37.9452 +- 2.76618      5       good
chromium@483296      40.6288 +- 2.1995       6       bad       <--
chromium@483298      36.0183 +- 14.5474      9       bad
chromium@483303      37.7904 +- 11.054       8       bad
chromium@483312      36.9202 +- 4.88975      6       bad
chromium@483351      37.7591 +- 11.7621      9       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/8974461138149845808


For feedback, file a bug with component Speed>Bisection

Comment 14 by scottmg@chromium.org, Jul 24 2017

Owner: ----
That CL is a Fuchsia-only test runner, so it couldn't have affected much of anything and especially not android.

Comment 15 by jgruber@chromium.org, Jul 25 2017

Cc: -scottmg@chromium.org
Owner: tzik@chromium.org
Status: Assigned (was: Untriaged)
Hmm, the bisect results in #13 seem to point at

commit 211d6bc6aacfeed4aa730418801c86c7cef6719c
Author: tzik <tzik@chromium.org>
Date:   Thu Jun 29 10:52:49 2017 +0900

    Notify RendererScheduler of starting LOADING phase on DidStartProvisionalLoad

tzik@, PTAL if that seems right. Bisection results are all very flaky prior to your CL.

Comment 16 by tzik@chromium.org, Jul 27 2017 

v8-gc-incremental-step_sum seems to take more time, but v8-gc-full-mark-compactor_sum takes less time after the CL, and the sum is not changed significantly. The GC mode probably switched?
https://chromeperf.appspot.com/report?sid=5cedb10a84728db86bce4befa77663a95caf2d5a94521028f6e7e61b6ef423bd&start_rev=480149&end_rev=487754

Comment 17 by jgruber@chromium.org, Jul 27 2017

Status: WontFix (was: Assigned)
Ah that makes sense, thanks. Let's close this one.
►

Sign in to add a comment