内存耗用:VSS/RSS/PSS/USS
http://hi.baidu.com/donghaozheng/blog/item/235da701ab70f60a1c95832e.html
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 leaksin a process.
For systems that have Python available, there is also a nice tool calledsmem 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
#
top | grep app名称
ps | grep app名称
procrank | grep app名称
dumpsys meminfo app名称
前两个命令只能查到VSS RSS内存占用信息
而后面两个命令可以查出 PSS USS内存占用.
dumpsys meminfo 可以查出native和dalvik分别占用多少内存
dumpsys 用来给出手机中所有应用程序的信息,并且也会给出现在手机的状态。
dumpsys [Option]
meminfo 显示内存信息
cpuinfo 显示CPU信息
account 显示accounts信息
activity 显示所有的activities的信息
window 显示键盘,窗口和它们的关系
wifi 显示wifi信息
内存耗用:VSS/RSS/PSS/USS相关推荐
- rss C语言,Android内存:VSS/RSS/PSS/USS介绍
一般来说内存占用大小有如下规律:VSS>=RSS>=PSS>=USS 1.VSS - Virtual Set Size(用处不大) 虚拟耗用内存(包含共享库占用的全部内存,以及分配但 ...
- 内存:VSS/RSS/PSS/USS区别和监控
软件开发的最后阶段就是测试,了解软件整体的cpu和mem使用情况,之前一直用ps来确定cpu使用率和rss内存,最近监控python多进程软件时,累积rss竟然超过了节点物理内存126G,原因在此处梳 ...
- 【转】内存耗用:VSS/RSS/PSS/USS
[转]内存耗用:VSS/RSS/PSS/USS Terms VSS- Virtual Set Size 虚拟耗用内存(包含共享库占用的内存) RSS- Resident Set Size 实际使用物理 ...
- 内存耗用:VSS/RSS/PSS/USS 介绍
参考:内存耗用:VSS/RSS/PSS/USS 的介绍 - 简书 内存耗用:VSS/RSS/PSS/USS_adaptiver的博客-CSDN博客_rss uss VSS- Virtual Set S ...
- android 内存uss rss,内存VSS/RSS/PSS/USS名词解释
VSS(virtual set size)虚拟耗用内存(包含共享库占用的内存) RSS(Resident set size)实际使用物理内存(包含共享库占用的内存) RSS是进程实际驻存在物理内存的部 ...
- linux中pss用法,[Linux] Memory: VSS/RSS/PSS/USS
Terms VSS- Virtual Set Size 虚拟耗用内存(包含共享库占用的内存) RSS- Resident Set Size 实际使用物理内存(包含共享库占用的内存) PSS- Prop ...
- linux vss rss区别,关于VSS / RSS / PSS / USS的解释是否准确?
我阅读了有关VSS / RSS / PSS / USS的说明: 这篇文章的目的是提供信息,以帮助解释来自各种工具的内存报告,以便可以确定Linux进程和系统的实际内存使用情况. Android有一个称 ...
- linux 进程的vss rss uss,内核/内存管理中的VSS/RSS/PSS/USS
转自:http://www.douban.com/note/161471809/ RSS is the total memory actually held in RAM for a process. ...
- 内存耗用:VSS/RSS/PSS/USS 的介绍
https://www.cnblogs.com/jycboy/p/5453533.html VSS:Virtual Set Size,虚拟耗用内存.它是一个进程能访问的所有内存空间地址的大小.这个大小 ...
最新文章
- python3语法错误-python3中的def函数语法错误
- 【Java】 剑指offer(36) 二叉搜索树与双向链表
- hdu 4640(状压dp)
- 拆解食饮新消费品牌的增长密码
- 学习总结——工作中的性能测试完整过程
- Python全栈开发之Django基础
- 监管科技崛起:从FinTech到RegTech
- 奎享添加自己字体_文泰刻绘怎么添加字体 新字体导入与添加步骤教程
- BCIduino脑电/肌电放大器结合eprime做实验流程说明
- 2018美赛建模总结+Latex标准美赛模板分享
- adventureworks mysql_AdventureWorks相关
- 今日头条的企业服务产品线
- 201912-3 化学方程式 的一种解法
- 手机虚拟摄像头_用手机当摄像头开直播 无他相机推荐
- 下载Youtube单个视频和播放列表的方法详细教程
- 硬盘出现“文件或目录损坏且无法读取”的故障,怎么解决?
- linux报错Error: /proc must be mounted
- 综述 - 染色质可及性与调控表观基因组 | Chromatin accessibility and the regulatory epigenome...
- VMI - 供应商管理库存
- Ceres库运行,模板内报内存冲突问题。(已解决)