New issue
Advanced search Search tips

Issue 748450 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.1% regression in system_health.memory_mobile at 488720:488787

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

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


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

android-nexus6
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_nexus6_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       : 5.77% | 3666403.71429 -> 3877815.14286

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/91c1a81d0e20427f1382b7fc6bd6786ef6564686..176a2b24fb23a0c9a3bc9eec27f6445dbfa5ab27


Revision                           Result                  N
chromium@488719                    3666404 +- 289813       14       good
chromium@488736                    3633860 +- 49901.4      6        good
chromium@488745                    3622652 +- 77281.4      14       good
chromium@488745,v8@ae9a2d38f3      3636260 +- 127501       21       good
chromium@488745,v8@56ebd492d6      3632544 +- 109349       14       good
chromium@488745,v8@91c1a81d0e      3640107 +- 121514       21       good
chromium@488745,v8@bb29f9a4d6      ---                     ---      build failure
chromium@488745,v8@176a2b24fb      3839665 +- 552486       14       bad
chromium@488745,v8@2bce488014      3845518 +- 390312       9        bad
chromium@488746                    3839666 +- 559606       21       bad
chromium@488747                    3831491 +- 462923       14       bad
chromium@488749                    3866230 +- 301601       9        bad
chromium@488753                    3896676 +- 1269.09      6        bad
chromium@488787                    3877815 +- 298616       14       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/8973105126339467584


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

Sign in to add a comment