New issue
Advanced search Search tips

Issue 747884 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1% regression in memory.top_10_mobile at 485916:486005

Project Member Reported by hjd@google.com, Jul 24 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 24 2017

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

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


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

android-nexus5
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 24 2017

Labels: Hotlist-Google
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jul 25 2017

Mergedinto: 745159
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Ken Rockot
  Commit : 474df01407e5d38c85364ae4d1709b8d9af16f16
  Date   : Wed Jul 12 13:28:56 2017
  Subject: Mojo C++ Bindings: Lazy Serialization

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
  Change       : 0.90% | 19897890.1429 -> 20076567.5714

Revision             Result                  N
chromium@485915      19897890 +- 574451      14      good
chromium@485929      19907597 +- 591751      21      good
chromium@485933      19908874 +- 316290      9       good
chromium@485934      19856056 +- 136521      6       good
chromium@485935      20108931 +- 339804      9       bad       <--
chromium@485939      20048566 +- 550428      21      bad
chromium@485961      20029259 +- 473465      21      bad
chromium@486005      20076568 +- 358245      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 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/8973191950594905584


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment