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

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

64.4%-291.5% regression in system_health.memory_mobile at 1529466330:1529482467

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=856050

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


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

health-plan-clankium-low-end-phone
health-plan-clankium-phone
perf-go-phone-512
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: go-phone-512-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/browse_social/browse_social_pinterest_infinite_scroll
  Change       : 191.85% | 669806.666667 -> 1954812.88889

Revision                                       Result                  N
android-chrome@009b09f963                      669807 +- 16190.9       9       good
android-chrome@009b09f963,chromium@568439      662980 +- 15863.7       6       good
android-chrome@009b09f963,chromium@568524      657860 +- 12541.4       6       good
android-chrome@009b09f963,chromium@568566      666393 +- 16190.9       9       good
android-chrome@009b09f963,chromium@568572      668100 +- 15939.8       14      good
android-chrome@009b09f963,chromium@568574      666393 +- 16190.9       9       good
android-chrome@009b09f963,chromium@568575      2585369 +- 1473213      6       bad       <--
android-chrome@009b09f963,chromium@568577      1634415 +- 1426432      9       bad
android-chrome@009b09f963,chromium@568587      2902354 +- 1257995      9       bad
android-chrome@6d7cb80987                      1954813 +- 1507668      9       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=browse.social.pinterest.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/8942759284564468512


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment