New issue
Advanced search Search tips

Issue 768040 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.3%-52% regression in system_health.memory_mobile at 502792:502840

Project Member Reported by benhenry@google.com, Sep 22 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 22 2017

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

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


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

android-webview-nexus5X
android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 23 2017

Mergedinto: 767243
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : perezju
  Commit : 08d6322ff7a5954b81a0a8024921e59f98efbb12
  Date   : Tue Sep 19 09:03:20 2017
  Subject: [Telemetry] Adjust wait after forcing Garbage Collection

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_news/load_news_irctc
  Change       : 53.54% | 5677397.33333 -> 8717312.0

Revision                                 Result                  N
chromium@502791                          5677397 +- 49970.1      6      good
chromium@502807                          5659648 +- 53326.7      6      good
chromium@502815                          5665792 +- 71180.9      6      good
chromium@502819                          5668523 +- 157966       6      good
chromium@502820                          5688320 +- 61780.4      6      good
chromium@502820,catapult@08d6322ff7      8701611 +- 114052       6      bad       <--
chromium@502821                          8674987 +- 73424.0      6      bad
chromium@502823                          8717312 +- 64243.2      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.irctc 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/8967714875998320128


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment