Terms
-
VSS - Virtual Set Size 虚拟耗用内存(包含共享库占用的内存)
-
RSS - Resident Set Size 实际使用物理内存(包含共享库占用的内存)
-
PSS - Proportional Set Size 实际使用的物理内存(比例分配共享库占用的内存)
-
USS - Unique Set Size 进程独自占用的物理内存(不包含共享库占用的内存)
一般来说内存占用大小有如下规律:VSS >= RSS >= PSS >= USS
Overview
The aim of this post is to provide information that will assist in interpreting memory reports from various tools so the true memory usage for Linux processes and the system can be determined.
Android has a tool called procrank (/system/xbin/procrank), which lists out the memory usage of Linux processes in order from highest to lowest usage. The sizes reported per process are VSS, RSS, PSS, and USS.
For the sake of simplicity in this description, memory will be expressed in terms of pages, rather than bytes. Linux systems like ours manage memory in 4096 byte pages at the lowest level.
VSS (reported as VSZ from ps) is the total accessible address space of a process. This size also includes memory that may not be resident in RAM like mallocs that have been allocated but not written to. VSS is of very little use for determing real memory usage of a process.
RSS is the total memory actually held in RAM for a process. RSS can be misleading, because it reports the total all of the shared libraries that the process uses, even though a shared library is only loaded into memory once regardless of how many processes use it. RSS is not an accurate representation of the memory usage for a single process.
PSS differs from RSS in that it reports the proportional size of its shared libraries, i.e. if three processes all use a shared library that has 30 pages, that library will only contribute 10 pages to the PSS that is reported for each of the three processes. PSS is a very useful number because when the PSS for all processes in the system are summed together, that is a good representation for the total memory usage in the system. When a process is killed, the shared libraries that contributed to its PSS will be proportionally distributed to the PSS totals for the remaining processes still using that library. In this way PSS can be slightly misleading, because when a process is killed, PSS does not accurately represent the memory returned to the overall system.
USS is the total private memory for a process, i.e. that memory that is completely unique to that process. USS is an extremely useful number because it indicates the true incremental cost of running a particular process. When a process is killed, the USS is the total memory that is actually returned to the system. USS is the best number to watch when initially suspicious of memory leaks in a process.
For systems that have Python available, there is also a nice tool called smem that will report memory statistics including all of these categories.
# procrank
procrank
PID Vss Rss Pss Uss cmdline
481 31536K 30936K 14337K 9956K system_server
475 26128K 26128K 10046K 5992K zygote
526 25108K 25108K 9225K 5384K android.process.acore
523 22388K 22388K 7166K 3432K com.android.phone
574 21632K 21632K 6109K 2468K com.android.settings
521 20816K 20816K 6050K 2776K jp.co.omronsoft.openwnn
474 3304K 3304K 1097K 624K /system/bin/mediaserver
37 304K 304K 289K 288K /sbin/adbd
29 720K 720K 261K 212K /system/bin/rild
601 412K 412K 225K 216K procrank
1 204K 204K 185K 184K /init
35 388K 388K 182K 172K /system/bin/qemud
284 384K 384K 160K 148K top
27 376K 376K 148K 136K /system/bin/vold
261 332K 332K 123K 112K logcat
33 396K 396K 105K 80K /system/bin/keystore
32 316K 316K 100K 88K /system/bin/installd
269 328K 328K 95K 72K /system/bin/sh
26 280K 280K 93K 84K /system/bin/servicemanager
45 304K 304K 91K 80K /system/bin/qemu-props
34 324K 324K 91K 68K /system/bin/sh
260 324K 324K 91K 68K /system/bin/sh
600 324K 324K 91K 68K /system/bin/sh
25 308K 308K 88K 68K /system/bin/sh
28 232K 232K 67K 60K /system/bin/debuggerd
#
相关推荐
本文将详细介绍如何使用ADB命令来查看内存(VSS,RSS,PSS,USS)以及CPU的使用情况。 首先,确保你已经正确地配置了ADB并成功连接到你的Android设备。配置ADB通常包括在电脑上安装Android SDK Platform Tools,并...
USS(Unique Set Size)表示进程独占的内存,PSS(Proportional Set Size)包括按比例的共享库,RSS(Resident Set Size)包括所有共享库,VSS(Virtual Set Size)则包含了未分配的实际物理内存。VSS、RSS、PSS和...
(Uss_Vss_Rss_Pss) PID Vss Rss Pss Uss cmdlineA 708 117204K 38304K 31315K 28956K /vendor/bin/hw/android.hardware.camera.provider@2.4-service 535 2187700K 37788K 23898K 21048K /system/bin/...
3. 使用procrank命令:procrank命令可以查看Android系统中各个进程的内存使用情况,包括PSS、USS、VSS和RSS等。通过观察USS的变化,可以更容易地发现内存泄露。 4. 使用脚本配合procrank:通过脚本定期调用procrank...
3. **Profiler Tools in Android Studio**:集成在Android Studio中的性能分析工具,包括Memory Profiler,可以实时监控应用的内存使用情况,包括VSS(虚拟集大小)、RSS(驻留集大小)、PSS(比例集大小)、USS...
procmem 给出了procrank中VSS、RSS、PSS、USS的每一部分组成,包括进程可执行程序本身、共享库、堆、栈的内存占用。这里的信息应该是从/proc/pid/maps文件中获取的.
在这些指标中,USS是最有用的指标之一,因为它反映了仅由当前进程独占使用的内存大小。当进程被终止时,USS所表示的内存将被完整回收。因此,在监测内存泄漏问题时,通常会重点关注USS值的变化趋势。 #### 五、...
### Android应用内存泄露详解 #### 一、内存泄露定义与理解 在Android开发过程中,内存泄露是一个常见的问题,尤其对于大型复杂的应用来说更是如此。内存泄露不仅会导致应用运行缓慢,严重时还会引起应用崩溃,极大...
在Android应用开发中,内存泄漏是一个严重的问题,它会导致应用程序占用过多内存,影响性能,甚至导致应用崩溃。本文档详细探讨了如何定位和规避Android App的内存泄漏。 首先,了解内存泄漏的基本概念至关重要。...
DDMS能够显示系统内存的整体分布,而procrank则提供了更详细的进程内存使用快照,包括PSS(Proportional Set Size)、USS(Unique Set Size)、VSS(Virtual Set Size)和RSS(Resident Set Size)。其中,USS是最能...
Procrank列出所有进程的内存占用情况,VSS、RSS、PSS和USS分别表示虚拟耗用内存、实际物理内存、比例分配的物理内存和进程独占的物理内存。在分析内存泄漏时,USS是一个重要的参考指标。 3. `dumpsys meminfo` 这...
一般来说,VSS >= RSS >= PSS >= USS。其中,USS 较小的原因是因为手机内存较小时,一般会将程序交由虚拟内存运行;程序所调用引入的接口类长度较大,占用内存高。 PSS 的重要性 PSS 是一个非常有用的数字,因为...
- **VSS (Virtual Set Size)**:虚拟内存大小,包含了进程使用的内存以及被共享的内存部分。 - **RSS (Resident Set Size)**:实际使用的物理内存大小,同样包含了被共享的内存。 - **PSS (Proportional Set Size...
在Android中,内存占用可以通过VSS(Virtual Set Size)、RSS(Resident Set Size)、PSS(Proportional Set Size)和USS(Unique Set Size)来衡量。这些指标反映了不同维度的内存使用情况,帮助我们理解应用对内存...