- 浏览: 485162 次
- 性别:
- 来自: 北京
文章分类
最新评论
-
alvin198761:
renzhengzhi 写道我参与过12306余票查询系统的开 ...
别给12306 辩解了 -
renzhengzhi:
我参与过12306余票查询系统的开发,用户请求被前面3层缓存拦 ...
别给12306 辩解了 -
renzhengzhi:
写的很好。
JAVA线程dump的分析 -
liyonghui160com:
说好的附件呢
分布式服务框架 Zookeeper -- 管理分布式环境中的数据 -
ghpaas:
orbeon作为xforms标准的实现,不论其设计器还是运行时 ...
XForms 1.1 中文翻译—第1章 关于XForms标准
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
#
发表评论
-
使用 RPM 打包软件,第 1 部分: 构建和分发包
2012-03-26 10:31 1292顾名思义,开源软件 ... -
用 RPM 打包软件,第 3 部分
2012-03-26 10:30 1175安装和卸载脚本的工作原理 安装和卸载脚本看起来很简单, ... -
用 RPM 打包软件,第 2 部分
2012-03-26 10:28 1185不作为 root 用户来构建 RPM 包 正如您在第 1 ... -
用 RPM 打包软件,第 1 部分
2012-03-26 10:23 986RPM(Red Hat Package Manager)是用于 ... -
Memory usage analysis
2010-09-03 23:33 1223Memory usage analysis Syste ... -
Linux: How to measure actual memory usage of an application or process?
2010-09-03 23:31 1281http://stackoverflow.com/questi ... -
HowTo: Profile Memory in a Linux System
2010-09-03 22:56 1187HOWTO: Profile Memory in a Li ... -
Linux内存管理机制
2010-09-03 22:48 2112内存是Linux内核所管理的最重要的资源之一,内存管理 ... -
linux内存管理概述
2010-09-03 22:44 2472Linux中的地址空间(一)有这么一系列的问题,是否在困扰 ... -
linux上buffer和cache的区别
2010-09-03 15:14 1528free free 命令相对于top 提供了更简洁的查看系统 ... -
linux下top命令参数解释
2010-09-03 14:56 893top命令是Linux下常用的性能分析工具,能够实时显示系统中 ... -
smem memory reporting tool
2010-08-25 15:41 979smem is a tool that can give ... -
Linux进程虚拟内存和物理内存
2010-08-25 15:39 5087先介绍几个基本概念: SIZE: 进程使用的 ... -
Linux 内核的文件 Cache 管理机制介绍
2010-08-18 18:21 10731 前言 自从诞生以来,Linux 就被不断完善和普及 ... -
运行时: 块内存复制,第 2 部分
2010-08-06 12:33 1260我的 前一专栏专注于 ... -
RunTime: 块内存复制
2010-08-06 12:32 1207内存复制 在计算机中,内存复制经常而普遍。它们出现在联网 ... -
内存详解
2010-08-06 11:34 964文档选项 ... -
Linux slab 分配器剖析
2010-08-06 11:32 1345良好的操作系统性能部分依赖于操作系统有效管理资源的能力。在 ... -
降低 Linux 内存开销
2010-08-06 11:30 1111Linux 广受追捧的一个优点是它比 Microsoft® ... -
在 Linux 平台中调试 C/C++ 内存泄漏方法
2010-08-06 11:29 1845由于 C 和 C++ 程序中完全由程序员自主申请和释放内存 ...
相关推荐
3. **Profiler Tools in Android Studio**:集成在Android Studio中的性能分析工具,包括Memory Profiler,可以实时监控应用的内存使用情况,包括VSS(虚拟集大小)、RSS(驻留集大小)、PSS(比例集大小)、USS...
VSS、RSS、PSS和USS之间存在递增关系。 Android内存分配采用Generational Heap Memory模型,分为Young Generation、Old Generation和Permanent Generation。Young Generation包含Eden和两个Survivor区,新生对象...
3. 使用procrank命令:procrank命令可以查看Android系统中各个进程的内存使用情况,包括PSS、USS、VSS和RSS等。通过观察USS的变化,可以更容易地发现内存泄露。 4. 使用脚本配合procrank:通过脚本定期调用procrank...
Procrank列出所有进程的内存占用情况,VSS、RSS、PSS和USS分别表示虚拟耗用内存、实际物理内存、比例分配的物理内存和进程独占的物理内存。在分析内存泄漏时,USS是一个重要的参考指标。 3. `dumpsys meminfo` 这...
- **PSS (Proportional Set Size)**:按比例计算的私有物理内存大小,考虑到了共享内存的平均分配。 - **USS (Unique Set Size)**:进程独有的物理内存大小,不包括共享内存。 在进行内存泄漏定位时,通常会重点...
定位内存泄漏通常需要深入代码分析,但也有工具辅助,例如使用MAT(Memory Analyzer Tool)或LeakCanary等,它们可以分析heap dump文件,找出长时间存在的对象链,帮助开发者定位可能导致泄漏的代码片段。...
- **PSS (Proportional Set Size)**:实际使用的物理内存,比例分配共享库占用的内存。 - **USS (Unique Set Size)**:进程独自占用的物理内存,不包括共享库占用的内存。 #### 三、实例分析 以“testAIDL”应用...
DDMS能够显示系统内存的整体分布,而procrank则提供了更详细的进程内存使用快照,包括PSS(Proportional Set Size)、USS(Unique Set Size)、VSS(Virtual Set Size)和RSS(Resident Set Size)。其中,USS是最能...