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

Issue 856100 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 855409
Owner: ----
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.7% regression in system_health.memory_mobile at 1529470636:1529482382

Project Member Reported by alexclarke@chromium.org, Jun 25 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 25 2018

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

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


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

health-plan-clankium-phone
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 26 2018

Mergedinto: 855409
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : James Darpinian
  Commit : d1b4ae2892b05cf622b3f649cb38b995ed2d1733
  Date   : Tue Jun 19 19:49:08 2018
  Subject: GPU: Don't flush when destroying transfer buffers.

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background_social/background_social_facebook
  Change       : 5.28% | 86396722.6667 -> 90958642.6667

Revision                                       Result                   N
android-chrome@009b09f963                      86396723 +- 94994.2      6      good
android-chrome@009b09f963,chromium@568439      87269000 +- 211427       6      good
android-chrome@009b09f963,chromium@568524      86960776 +- 396373       6      good
android-chrome@009b09f963,chromium@568566      87239645 +- 290028       6      good
android-chrome@009b09f963,chromium@568572      86979891 +- 148048       6      good
android-chrome@009b09f963,chromium@568574      87234867 +- 227625       6      good
android-chrome@009b09f963,chromium@568575      91104051 +- 490564       6      bad       <--
android-chrome@009b09f963,chromium@568577      90883549 +- 564606       6      bad
android-chrome@009b09f963,chromium@568587      90532659 +- 736974       6      bad
android-chrome@6d7cb80987                      90464904 +- 329574       6      bad
android-chrome@6c8f6fc4ae                      90958643 +- 541275       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.social.facebook 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/8942755557299840288


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment