New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 797038 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

2.3%-7.1% regression in memory.top_10_mobile at 525310:525407

Project Member Reported by briander...@chromium.org, Dec 21 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 21 2017

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

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


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

android-nexus5X
android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 22 2017

Cc: yangguo@chromium.org
Owner: yangguo@chromium.org
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author yangguo@chromium.org ===

Hi yangguo@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Yang Guo
  Commit : 9c6bc7afc0f8a62e24df92d72e41f2f9d590e023
  Date   : Wed Dec 20 07:34:39 2017
  Subject: Leave spaces between instance types.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_chrome/load_chrome_blank
  Change       : 7.40% | 16173328.0 -> 17370554.6667

Revision                           Result                   N
chromium@525337                    16173328 +- 479783       6      good
chromium@525342                    16102843 +- 418649       6      good
chromium@525344                    16115586 +- 1460405      9      good
chromium@525344,v8@9c6bc7afc0      17267301 +- 578370       6      bad       <--
chromium@525344,v8@c293bc010b      17227195 +- 766109       6      bad
chromium@525344,v8@bf691e79d7      17411856 +- 840490       6      bad
chromium@525345                    17032976 +- 1256751      9      bad
chromium@525346                    17230608 +- 501896       6      bad
chromium@525355                    17024784 +- 1135165      6      bad
chromium@525372                    17002256 +- 1152578      6      bad
chromium@525407                    17370555 +- 802938       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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.chrome.blank system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection
Mergedinto: 797045
Status: Duplicate (was: Assigned)

Sign in to add a comment