New issue
Advanced search Search tips

Issue 731061 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

6.6% regression in system_health.memory_mobile at 477636:477688

Project Member Reported by primiano@chromium.org, Jun 8 2017

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglpTv9ggM


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

android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 10 2017

Mergedinto: 731648
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : hpayer
  Commit : cf8f7bdc9d5ee314a10fe043e421ec95604d4eca
  Date   : Wed Jun 07 13:21:28 2017
  Subject: [heap] Increase memory reducer activation limit for external memory changes.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_washingtonpost
  Change       : 4.65% | 61327282.6667 -> 64178952.0

Revision                           Result                   N
chromium@477635                    61327283 +- 872023       6      good
chromium@477662                    61506312 +- 1511979      6      good
chromium@477675                    61402205 +- 897621       6      good
chromium@477677                    61423027 +- 655459       6      good
chromium@477677,v8@f2cd359ac9      61366707 +- 824430       6      good
chromium@477677,v8@d2066154c8      61285128 +- 1181129      6      good
chromium@477677,v8@cf8f7bdc9d      63860147 +- 1435242      6      bad       <--
chromium@477678                    63651251 +- 1119540      6      bad
chromium@477679                    64255411 +- 1714384      6      bad
chromium@477682                    63752968 +- 1226639      6      bad
chromium@477688                    64178952 +- 1152059      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=browse.news.washingtonpost system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8977357304570642896

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5514092636274688


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Sign in to add a comment