New issue
Advanced search Search tips

Issue 681653 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% regression in memory.top_10_mobile at 443442:443514

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

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


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

android-nexus9
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 17 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
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 0.75% | 12874920.0 -> 12849977.1429

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/bea6ff95471b7a3da8030b0903d73e48434cc18a..2c22f5c684f13a4b7b9eeb3ff7007e80e5b1e8b0


Revision             Result                  N
chromium@443441      12874920 +- 504761      14       good
chromium@443484      12889770 +- 234637      14       good
chromium@443497      12869601 +- 273970      14       good
chromium@443498      ---                     ---      build failure
chromium@443499      12824349 +- 143495      14       bad
chromium@443514      12849977 +- 174678      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.en.m.wikipedia.org.wiki.Science memory.top_10_mobile

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

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


| 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