New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 778675 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-1.6% regression in system_health.memory_mobile at 511079:511231

Project Member Reported by petermarshall@chromium.org, Oct 26 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 26 2017

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

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


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

android-nexus5
android-nexus6
android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 26 2017

Cc: danno@chromium.org
Owner: danno@chromium.org
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author danno@chromium.org ===

Hi danno@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Daniel Clifford
  Commit : b590679496e829fd2f88ba4494072f0196c979de
  Date   : Tue Oct 24 09:05:16 2017
  Subject: Activate CSA implementation of Array.prototype.slice

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_tools/load_tools_docs
  Change       : 0.71% | 1650818.66667 -> 1662461.33333

Revision                           Result                  N
chromium@511078                    1650819 +- 14.6059      6      good
chromium@511148                    1654104 +- 11.3137      6      good
chromium@511157                    1654107 +- 18.4752      6      good
chromium@511162                    1654103 +- 17.5879      6      good
chromium@511162,v8@598623c6b9      1654108 +- 9.79796      6      good
chromium@511162,v8@b590679496      1662460 +- 21.9089      6      bad       <--
chromium@511162,v8@bb6bee3255      1662461 +- 9.2376       6      bad
chromium@511163                    1662463 +- 7.30297      6      bad
chromium@511164                    1662460 +- 18.7617      6      bad
chromium@511166                    1662459 +- 21.6641      6      bad
chromium@511183                    1662463 +- 7.30297      6      bad
chromium@511217                    1662461 +- 9.2376       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.tools.docs 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/8964662809388331600


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Oct 27 2017

Issue 778614 has been merged into this issue.
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Oct 27 2017

Issue 778676 has been merged into this issue.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 28 2017

Cc: kraynov@chromium.org
 Issue 778613  has been merged into this issue.
Components: Speed>Metrics>SystemHealthRegressions
Components: -Speed>Metrics>SystemHealthRegressions

Sign in to add a comment