New issue
Advanced search Search tips

Issue 748447 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.4% regression in system_health.memory_mobile at 488741:488859

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=748447

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


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

android-nexus5
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 25 2017

Labels: Hotlist-Google
Project Member

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


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_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.96% | 3650183.11111 -> 3897023.33333

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/91c1a81d0e20427f1382b7fc6bd6786ef6564686..7cfd0c249ec6724ee4f5c55fe4f4975b1b327596


Revision                           Result                  N
chromium@488740                    3650183 +- 65559.6      9        good
chromium@488744                    3637327 +- 64669.1      9        good
chromium@488745                    3646596 +- 96578.6      14       good
chromium@488745,v8@ae9a2d38f3      3648958 +- 71985.5      9        good
chromium@488745,v8@91c1a81d0e      3633743 +- 106494       14       good
chromium@488745,v8@bb29f9a4d6      ---                     ---      build failure
chromium@488745,v8@176a2b24fb      ---                     ---      build failure
chromium@488745,v8@6d9025ef57      ---                     ---      build failure
chromium@488745,v8@7cfd0c249e      3849054 +- 591956       14       bad
chromium@488745,v8@99bbf7b743      3857765 +- 523834       14       bad
chromium@488746                    3875392 +- 292168       14       bad
chromium@488748                    3866977 +- 299366       9        bad
chromium@488755                    3896977 +- 202.754      6        bad
chromium@488770                    3867131 +- 297688       9        bad
chromium@488800                    3896973 +- 238.49       6        bad
chromium@488859                    3897023 +- 212.597      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/8973105250308368704


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)
This came back down.

Sign in to add a comment