New issue
Advanced search Search tips

Issue 865679 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 863530
Owner: ----
Closed: Jul 20
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

109.5%-190.5% regression in system_health.memory_mobile at 1530653166:1531279570

Project Member Reported by npm@chromium.org, Jul 19

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=865679

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


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

perf-go-phone-512
Mergedinto: 863530
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Khushal
  Commit : 81a71217973e595b574783c2496629311051450f
  Date   : Mon Jul 09 22:48:23 2018
  Subject: gpu: Add memory tracing for ServiceTransferCache.

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/load_media/load_media_imgur
  Change       : 566.78% | 1239150.66667 -> 8262359.33333

Revision                                       Result                  N
android-chrome@5cb3f5852f                      1239151 +- 545581       6      good
android-chrome@7f8fc8ca89                      1352815 +- 466704       6      good
android-chrome@45a49de40d                      1614617 +- 607898       6      good
android-chrome@5060b21f7f                      1465796 +- 321060       6      good
android-chrome@96555ff9c3                      1371588 +- 658236       6      good
android-chrome@96555ff9c3,chromium@573466      1370223 +- 747338       9      good
android-chrome@96555ff9c3,chromium@573486      1615983 +- 609270       6      good
android-chrome@96555ff9c3,chromium@573491      654788 +- 0.0           6      good
android-chrome@96555ff9c3,chromium@573494      1745689 +- 620160       6      good
android-chrome@96555ff9c3,chromium@573495      1635097 +- 907749       6      good
android-chrome@96555ff9c3,chromium@573496      8034349 +- 801673       6      bad       <--
android-chrome@96555ff9c3,chromium@573506      8134359 +- 561051       6      bad
android-chrome@96555ff9c3,chromium@573545      8654210 +- 733465       6      bad
android-chrome@0c23a72c68                      7526969 +- 2630011      9      bad
android-chrome@7b94b395a3                      8149037 +- 877557       6      bad
android-chrome@b291a7ceb9                      8240514 +- 402951       6      bad
android-chrome@801e0585fe                      8262359 +- 605796       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.media.imgur 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/8940541655743349216


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment