New issue
Advanced search Search tips

Issue 681591 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.2% regression in memory.top_10_mobile_stress at 443317:443441

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=681591

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


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

android-nexus9
Project Member

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


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 1.59% | 12533442.2857 -> 12732363.4286

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/81c62e070b8656432899fc17b46b882bfcf1d59a..9884fb91e15e5e85218886b67af410668a08c38b


Revision                           Result                   N
chromium@443317                    12533442 +- 617777       14       good
chromium@443379                    12339932 +- 565798       6        good
chromium@443395                    12418169 +- 535040       9        good
chromium@443399                    12359549 +- 536309       9        good
chromium@443400                    12433829 +- 792155       9        good
chromium@443400,v8@2bca05685f      12319651 +- 1137689      14       good
chromium@443400,v8@81c62e070b      12597543 +- 417882       14       good
chromium@443400,v8@29e6218b7f      ---                      ---      build failure
chromium@443400,v8@9884fb91e1      12798725 +- 566321       14       bad
chromium@443400,v8@aa75904e3c      12664510 +- 382131       9        bad
chromium@443401                    12792069 +- 350070       6        bad
chromium@443403                    12764784 +- 339944       6        bad
chromium@443410                    12761860 +- 538484       9        bad
chromium@443441                    12732363 +- 778571       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=http.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile_stress

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

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


| 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!
Status: WontFix (was: Untriaged)
Only nexus9. Wontfix.
Labels: Performance-Memory

Sign in to add a comment