New issue
Advanced search Search tips

Issue 747807 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 747802
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

74% regression in v8.runtimestats.browsing_mobile at 488695:488766

Project Member Reported by jarin@google.com, Jul 24 2017

Issue description

Could this be the parallel scavenge?
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 24 2017

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

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


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

android-webview-nexus5X
Could be, lets wait for the bisects. 
Just checked again: 'v8-gc-phantom-handle-callback_sum' also regresses and I do not yet see how this could be affected by my changes. Bisects should tell us more.
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 24 2017

Labels: Hotlist-Google
Project Member

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

Mergedinto: 747802
Status: Duplicate (was: Assigned)

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 176a2b24fb23a0c9a3bc9eec27f6445dbfa5ab27
  Date   : Wed Jul 19 13:04:47 2017
  Subject: [heap] Reland "[heap] Allow a minimum semi-space size of 512K."

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : GC:duration_avg/browse_social/browse_social_instagram
  Change       : 58.49% | 142.860833333 -> 226.422833333

Revision                           Result                  N
chromium@488694                    142.861 +- 37.6278      6      good
chromium@488730                    138.378 +- 16.993       6      good
chromium@488739                    143.595 +- 19.0259      6      good
chromium@488744                    127.071 +- 7.50403      6      good
chromium@488745                    130.53 +- 11.371        6      good
chromium@488745,v8@ae9a2d38f3      137.417 +- 22.3992      6      good
chromium@488745,v8@91c1a81d0e      143.001 +- 34.9948      6      good
chromium@488745,v8@bb29f9a4d6      136.589 +- 19.3361      6      good
chromium@488745,v8@176a2b24fb      208.312 +- 13.1327      6      bad       <--
chromium@488745,v8@7cfd0c249e      208.465 +- 10.7409      6      bad
chromium@488745,v8@b23b8c088c      213.528 +- 13.871       6      bad
chromium@488746                    233.083 +- 16.3175      6      bad
chromium@488748                    221.83 +- 13.5714       6      bad
chromium@488766                    226.423 +- 18.6985      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.instagram 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/8973206108616617664


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

Comment 8 by 42576172...@developer.gserviceaccount.com, Jul 25 2017


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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 176a2b24fb23a0c9a3bc9eec27f6445dbfa5ab27
  Date   : Wed Jul 19 13:04:47 2017
  Subject: [heap] Reland "[heap] Allow a minimum semi-space size of 512K."

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : GC:duration_avg/browse_social/browse_social_instagram
  Change       : 61.69% | 138.0685 -> 223.236833333

Revision                           Result                  N
chromium@488694                    138.069 +- 17.0423      6      good
chromium@488730                    138.924 +- 20.9477      6      good
chromium@488739                    130.548 +- 7.77168      6      good
chromium@488744                    135.382 +- 7.20741      6      good
chromium@488745                    140.378 +- 29.0204      6      good
chromium@488745,v8@ae9a2d38f3      136.571 +- 29.1501      6      good
chromium@488745,v8@91c1a81d0e      141.772 +- 32.1833      6      good
chromium@488745,v8@bb29f9a4d6      137.853 +- 29.2662      6      good
chromium@488745,v8@176a2b24fb      210.4 +- 15.6375        6      bad       <--
chromium@488745,v8@7cfd0c249e      206.057 +- 14.0554      6      bad
chromium@488745,v8@b23b8c088c      206.535 +- 9.25444      6      bad
chromium@488746                    226.65 +- 12.2276       6      bad
chromium@488748                    229.125 +- 22.8024      6      bad
chromium@488766                    223.237 +- 18.1904      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.instagram 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/8973206099342550064


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment