New issue
Advanced search Search tips

Issue 752174 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 751052
Owner:
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.3% regression in system_health.memory_mobile at 489965:490074

Project Member Reported by ulan@google.com, Aug 3 2017

Issue description

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

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


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

android-nexus7v2
Mergedinto: 751052
Status: Duplicate (was: Assigned)

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 2cc8fdfb47226101b958da465d64803368fb7c76
  Date   : Thu Jul 27 11:09:24 2017
  Subject: [heap] Re-implement weak cell tracking in the marker.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_yahoo
  Change       : 2.67% | 5060164.0 -> 5158235.14286

Revision                           Result                  N
chromium@489964                    5060164 +- 69929.2      9       good
chromium@490019                    5074396 +- 104306       14      good
chromium@490026                    5062133 +- 42971.5      9       good
chromium@490027                    5055368 +- 76132.7      9       good
chromium@490027,v8@2cc8fdfb47      5197911 +- 148433       6       bad       <--
chromium@490027,v8@6a75fcd4df      5210836 +- 172070       6       bad
chromium@490027,v8@e4bbf92be3      5207949 +- 217428       6       bad
chromium@490027,v8@9836cdb1ad      5193493 +- 179946       6       bad
chromium@490028                    5214985 +- 178592       6       bad
chromium@490030                    5186921 +- 290264       14      bad
chromium@490033                    5183442 +- 320600       14      bad
chromium@490047                    5188926 +- 375068       21      bad
chromium@490074                    5158235 +- 319471       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=load.search.yahoo 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/8972264561735907152


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment