New issue
Advanced search Search tips

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

11.8%-18.2% regression in system_health.memory_mobile at 477636:477689

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

Issue description

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

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


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

android-webview-nexus5X
android-webview-nexus6
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_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_washingtonpost
  Change       : 19.46% | 7748187.33333 -> 9256350.66667

Revision                           Result                 N
chromium@477640                    7748187 +- 283667      6      good
chromium@477665                    7832866 +- 180559      6      good
chromium@477677                    7722224 +- 267976      6      good
chromium@477677,v8@f2cd359ac9      7788518 +- 402350      6      good
chromium@477677,v8@d2066154c8      7821659 +- 392781      6      good
chromium@477677,v8@cf8f7bdc9d      9181919 +- 348229      6      bad       <--
chromium@477678                    9181375 +- 203399      6      bad
chromium@477679                    9185919 +- 301881      6      bad
chromium@477680                    9171661 +- 205354      6      bad
chromium@477683                    9230989 +- 307036      6      bad
chromium@477689                    9256351 +- 374698      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/8977268423285205872

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


| 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