New issue
Advanced search Search tips

Issue 681588 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

2.3% regression in memory.top_10_mobile_stress at 443346:443464

Project Member Reported by nzolghadr@chromium.org, Jan 16 2017

Issue description

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 16 2017

Mergedinto: 681541
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : mvstanton
  Commit : b8294aaa978e972978b8d82cedf63befad5d7af1
  Date   : Thu Jan 12 11:29:09 2017
  Subject: [TypeFeedbackVector] Root literal arrays in function literals slots

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_www_baidu_com_s_word_google
  Change       : 1.76% | 7777234.66667 -> 7913762.66667

Revision                           Result                  N
chromium@443346                    7777235 +- 131945       6      good
chromium@443375                    7784952 +- 129170       6      good
chromium@443390                    7809911 +- 175075       6      good
chromium@443397                    7738593 +- 98692.1      6      good
chromium@443399                    7740927 +- 111848       6      good
chromium@443400                    7755128 +- 112093       6      good
chromium@443400,v8@2bca05685f      7800572 +- 128523       6      good
chromium@443400,v8@b8294aaa97      7912751 +- 85074.7      6      bad       <--
chromium@443400,v8@81c62e070b      7891324 +- 140096       9      bad
chromium@443400,v8@9884fb91e1      7943200 +- 19557.4      6      bad
chromium@443400,v8@aa75904e3c      7941651 +- 18294.1      6      bad
chromium@443401                    8022259 +- 484245       6      bad
chromium@443404                    7922224 +- 70811.4      6      bad
chromium@443464                    7913763 +- 85511.5      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 --story-filter=http.www.baidu.com.s.word.google memory.top_10_mobile_stress

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

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


| 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 Tests>AutoBisect.  Thank you!

Sign in to add a comment