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

Issue 856063 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

1.4% 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=856063

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


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

health-plan-clankium-phone
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 25 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:private_dirty_size_avg/load_games/load_games_lazors
  Change       : 2.44% | 44518194.6667 -> 45604317.3333

Revision                                       Result                   N
android-chrome@009b09f963                      44518195 +- 113058       6      good
android-chrome@009b09f963,chromium@568439      44508637 +- 203232       6      good
android-chrome@009b09f963,chromium@568524      44516147 +- 99032.3      6      good
android-chrome@009b09f963,chromium@568566      44517512 +- 136901       6      good
android-chrome@009b09f963,chromium@568572      44720264 +- 227997       6      good
android-chrome@009b09f963,chromium@568574      44619229 +- 120472       6      good
android-chrome@009b09f963,chromium@568575      45569501 +- 149976       6      bad       <--
android-chrome@009b09f963,chromium@568577      45669171 +- 144808       6      bad
android-chrome@009b09f963,chromium@568587      45717640 +- 123635       6      bad
android-chrome@6d7cb80987                      45603635 +- 70739.6      6      bad
android-chrome@6c8f6fc4ae                      45604317 +- 163787       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=load.games.lazors 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/8942758504242547280


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment