New issue
Advanced search Search tips

Issue 754256 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

2.2%-3.4% regression in memory.top_10_mobile at 482796:482921

Project Member Reported by primiano@chromium.org, Aug 10 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 10 2017

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

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


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

android-nexus5
android-nexus5X
android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 11 2017

Mergedinto: 752178
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Toon Verwaest
  Commit : e91c6dc7a9d3cdd37fc572f69625123b6564c0e0
  Date   : Tue Jun 27 12:25:22 2017
  Subject: [dictionary] Move Name into PropertyCell to save space in overallocated hashtable

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_www_google_co_uk_hl_en_q_science
  Change       : 2.35% | 3041108.66667 -> 3112634.0

Revision                           Result                  N
chromium@482795                    3041109 +- 1111.11      6      good
chromium@482839                    3037970 +- 27608.3      6      good
chromium@482861                    3044186 +- 28089.7      6      good
chromium@482864                    3035917 +- 19712.8      6      good
chromium@482864,v8@189c8263e5      3024231 +- 776.385      6      good
chromium@482864,v8@e91c6dc7a9      3133220 +- 53075.2      6      bad       <--
chromium@482864,v8@8060b9cc45      3113224 +- 18878.5      6      bad
chromium@482864,v8@095132d67a      3109138 +- 18168.6      6      bad
chromium@482864,v8@ab028038db      3111680 +- 17442.1      6      bad
chromium@482865                    3120231 +- 42453.9      6      bad
chromium@482866                    3111273 +- 39897.4      6      bad
chromium@482867                    3113020 +- 19222.5      6      bad
chromium@482872                    3106969 +- 19417.4      6      bad
chromium@482883                    3112634 +- 29343.4      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8971643844810898800


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment