New issue
Advanced search Search tips

Issue 787446 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 780749



Sign in to add a comment

38.3%-167.2% regression in v8.browsing_mobile at 515925:516019

Project Member Reported by ulan@google.com, Nov 21 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 21 2017

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=4db6313b85fdfa529a46a5465c63dd802eb4ae837312286056214fd074fd5c61


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

android-nexus5
android-nexus5X
android-webview-nexus5X
android-webview-nexus6
chromium-rel-mac11-air
chromium-rel-win7-gpu-ati
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 22 2017

Cc: mlippautz@chromium.org
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)

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

Hi mlippautz@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 : Michael Lippautz
  Commit : 667555c6b8dadcfe4e592fe06bb6846468b8141e
  Date   : Thu Nov 09 17:29:11 2017
  Subject: [heap] Remove independent handles

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_social/browse_social_instagram
  Change       : 121.93% | 6.1315 -> 13.6075

Revision                           Result                   N
chromium@515924                    6.1315 +- 1.85093        6      good
chromium@515942                    5.42933 +- 0.865877      6      good
chromium@515951                    6.228 +- 2.6421          6      good
chromium@515951,v8@2328e4d196      6.33533 +- 3.5862        6      good
chromium@515951,v8@616be20ebc      6.53067 +- 2.41135       6      good
chromium@515951,v8@ff4e4ab4b6      6.12367 +- 0.859018      6      good
chromium@515951,v8@667555c6b8      14.0642 +- 0.74793       6      bad       <--
chromium@515951,v8@02c84d4192      13.3125 +- 2.46662       6      bad
chromium@515951,v8@359e69e183      14.4185 +- 3.39309       6      bad
chromium@515952                    14.577 +- 2.31318        6      bad
chromium@515953                    13.3055 +- 0.812029      6      bad
chromium@515954                    14.2633 +- 3.41025       6      bad
chromium@515956                    13.4013 +- 1.17739       6      bad
chromium@515960                    13.6075 +- 0.732323      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.social.instagram v8.browsing_mobile

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

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


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

Comment 4 by 42576172...@developer.gserviceaccount.com, Nov 22 2017

 Issue 787433  has been merged into this issue.
Blocking: 780749
Cc: -mlippautz@chromium.org
Components: Blink>Bindings
Cc: jgruber@chromium.org
 Issue 790977  has been merged into this issue.
Status: Archived (was: Assigned)

Sign in to add a comment