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

Issue 780218 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

2.4% regression in system_health.memory_mobile at 511929:512062

Project Member Reported by briander...@chromium.org, Oct 31 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 31 2017

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

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


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

android-nexus5
Mergedinto: 779798
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Marijn Kruisselbrink
  Commit : df51989616e170eef04e72779d0d7e5c3ee5980a
  Date   : Thu Oct 26 19:52:57 2017
  Subject: Turn mojo blobs on by default.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_washingtonpost
  Change       : 1.66% | 25717541.0 -> 26145538.8571

Revision             Result                   N
chromium@511928      25717541 +- 296085       14      good
chromium@511929      25877260 +- 768895       21      bad       <--
chromium@511930      25950348 +- 1094974      21      bad
chromium@511931      25854518 +- 597203       14      bad
chromium@511933      25935724 +- 756359       14      bad
chromium@511937      25864082 +- 510737       9       bad
chromium@511945      26064446 +- 223070       6       bad
chromium@511962      25895743 +- 522758       14      bad
chromium@511995      26039384 +- 1299194      9       bad
chromium@512062      26145539 +- 1905125      14      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.washingtonpost 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/8964184580072520080


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment