New issue
Advanced search Search tips

Issue 781823 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.3%-7.2% regression in system_health.memory_mobile at 513646:513746

Project Member Reported by mustaq@chromium.org, Nov 6 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=781823

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


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

android-nexus5X
android-webview-nexus5X
android-webview-nexus6
Cc: u...@chromium.org
Owner: u...@chromium.org
Status: Assigned (was: Untriaged)

=== 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 Degenbaev
  Commit : 586067e45dd542a117b67ad66d3b14475d8d571f
  Date   : Thu Nov 02 19:10:00 2017
  Subject: Reland "[heap] Temporarily disable concurrent marking."

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_cnn
  Change       : 6.23% | 35765627.8333 -> 37994867.3333

Revision                           Result                   N
chromium@513719                    35765628 +- 892232       6      good
chromium@513719,v8@a274fc6536      35777470 +- 1284282      6      good
chromium@513719,v8@694a18781c      35944096 +- 1629975      6      good
chromium@513719,v8@586067e45d      38097491 +- 1332970      6      bad       <--
chromium@513720                    38098078 +- 606480       6      bad
chromium@513721                    38118736 +- 1387334      6      bad
chromium@513722                    38053089 +- 942589       6      bad
chromium@513724                    37975946 +- 605335       6      bad
chromium@513729                    37775989 +- 1201397      6      bad
chromium@513738                    37994867 +- 1388948      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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.news.cnn system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection
 Issue 781812  has been merged into this issue.
 Issue 781808  has been merged into this issue.
 Issue 781795  has been merged into this issue.
 Issue 781795  has been merged into this issue.
 Issue 781817  has been merged into this issue.
Cc: rmcilroy@chromium.org
 Issue 782798  has been merged into this issue.
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Nov 17 2017

 Issue 786394  has been merged into this issue.

Comment 11 by u...@chromium.org, Nov 21 2017

Status: Fixed (was: Assigned)
The concurrent marker was re-enabled.
Project Member

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

 Issue 787442  has been merged into this issue.

Sign in to add a comment