New issue
Advanced search Search tips

Issue 748461 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

7% regression in system_health.memory_mobile at 488660:488861

Project Member Reported by hjd@google.com, Jul 25 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-nexus5X
Project Member

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

Mergedinto: 747802
Status: Duplicate (was: Untriaged)

=== 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_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_ebay
  Change       : 6.92% | 3652735.11111 -> 3902069.33333

Revision                           Result                  N
chromium@488659                    3652735 +- 58893.9      9      good
chromium@488710                    3651446 +- 57377.0      9      good
chromium@488735                    3642255 +- 78564.9      9      good
chromium@488742                    3641179 +- 50107.3      6      good
chromium@488745                    3659571 +- 45865.3      6      good
chromium@488745,v8@ae9a2d38f3      3644688 +- 64586.0      6      good
chromium@488745,v8@91c1a81d0e      3660449 +- 52856.2      6      good
chromium@488745,v8@bb29f9a4d6      3633098 +- 58412.1      6      good
chromium@488745,v8@176a2b24fb      3911313 +- 2236.14      6      bad       <--
chromium@488745,v8@7cfd0c249e      3910869 +- 324.637      6      bad
chromium@488745,v8@b23b8c088c      3923163 +- 47949.4      6      bad
chromium@488746                    3902759 +- 37269.3      6      bad
chromium@488747                    3895489 +- 1921.86      6      bad
chromium@488748                    3908881 +- 48291.0      6      bad
chromium@488760                    3865517 +- 300560       9      bad
chromium@488861                    3902069 +- 37968.0      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.ebay 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/8973104326630692832


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment