New issue
Advanced search Search tips

Issue 755650 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

8.2% regression in system_health.memory_mobile at 493318:493382

Project Member Reported by ericrk@chromium.org, Aug 15 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 15 2017

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

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


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

android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 15 2017

Mergedinto: 755089
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : d09f9c424fbc0c5679fd7c370c70c8915b29d987
  Date   : Thu Aug 10 08:56:49 2017
  Subject: [runtime] Do not clear prototype map descriptors.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/browse_social/browse_social_tumblr_infinite_scroll
  Change       : 5.41% | 54856083.619 -> 57824599.8095

Revision                           Result                    N
chromium@493317                    54856084 +- 12082914      21      good
chromium@493350                    54257474 +- 2290840       6       good
chromium@493366                    54633803 +- 4344335       14      good
chromium@493370                    54272989 +- 5628735       14      good
chromium@493370,v8@80423e89b1      54397452 +- 2361471       6       good
chromium@493370,v8@d09f9c424f      56845942 +- 4128134       9       bad       <--
chromium@493371                    57384731 +- 4896354       6       bad
chromium@493372                    57525970 +- 4355672       6       bad
chromium@493374                    57492660 +- 10929702      14      bad
chromium@493382                    57824600 +- 13470285      21      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.tumblr.infinite.scroll 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/8971169710061639104


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment