android 記憶體監控 procrank vss pss

通過 pss 和 uss 來查看進程使用的記憶體情況
在模擬器上 adb shell procrank 可以查看到以下資訊
zhengs-MacBook-Air:~ yajun0601$ adb shell
shell@android:/ $ procrank -p                                                 
warning: could not read usage for 2698
  PID      Vss      Rss      Pss      Uss  cmdline
 2016   78832K   64164K   44719K   43628K  system_server
 3801   61348K   61208K   39134K   37648K  android.process.acore
 2213  190408K   48296K   29257K   28352K  com.cyanogenmod.trebuchet
 2113   74216K   44292K   25702K   24816K  com.android.systemui
 2179   38532K   38420K   20892K   20032K  com.sohu.inputmethod.sogou
 2199   38148K   35016K   17414K   16740K  com.android.phone
25599   57616K   39628K   16420K   14680K  com.zdworks.android.zdclock:zdclock
24931   29920K   29840K   13524K   12964K  com.wali.NetworkAssistant
 3447   34072K   33988K   12113K   11024K  com.wandoujia.phoen
下面解釋這四項：
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.