New issue
Advanced search Search tips

Issue 747917 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

3.7% regression in system_health.memory_mobile at 488678:488775

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

Issue description

See the link to graphs below.
 
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=747917

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


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

android-one
Project Member

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

Labels: Hotlist-Google
Project Member

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

Mergedinto: 747806
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 858052930221bf05230d8e0eb0e681bf9b532980
  Date   : Thu Jul 20 13:47:22 2017
  Subject: [heap] Remove clearing of caches and counter of shared function info in

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_social/browse_social_instagram
  Change       : 4.31% | 11462293.3333 -> 11956749.3333

Revision                           Result                   N
chromium@488677                    11462293 +- 642926       9       good
chromium@488726                    11288891 +- 77909.3      6       good
chromium@488739                    11484560 +- 765549       9       good
chromium@488745                    11458359 +- 636963       9       good
chromium@488745,v8@b23b8c088c      11254433 +- 240169       6       good
chromium@488745,v8@1084d20978      11332436 +- 474220       9       good
chromium@488745,v8@b30ea1646a      11304405 +- 112378       6       good
chromium@488745,v8@8580529302      11811131 +- 512487       6       bad       <--
chromium@488745,v8@ecd06ed09f      11757745 +- 865346       14      bad
chromium@488745,v8@f24b6f96f8      11863045 +- 542111       9       bad
chromium@488745,v8@8ab48b6c04      11770913 +- 504830       6       bad
chromium@488746                    11880821 +- 491330       9       bad
chromium@488747                    11867682 +- 91798.3      9       bad
chromium@488748                    11834283 +- 646317       14      bad
chromium@488751                    11812833 +- 527102       9       bad
chromium@488775                    11956749 +- 264498       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=browse.social.instagram 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/8973190740763902384


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment