使用pmap&smem排查内存问题


VSS、RSS、PSS、USS

  • VSS - Virtual Set Size 虚拟耗用内存(包含共享库占用的内存)
  • RSS - Resident Set Size 实际使用物理内存(包含共享库占用的内存)
  • PSS - Proportional Set Size 实际使用的物理内存(比例分配共享库占用的内存)
  • USS - Unique Set Size 进程独自占用的物理内存(不包含共享库占用的内存)

英文解释

  • 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.

smaps文件

The /proc/[pid]/smaps file is present only if the
CONFIG_PROC_PAGE_MONITOR kernel configuration option is
enabled.

smemcap

  • smemcap可以用于嵌入式设备
    Embedded Usage
    To capture memory statistics on resource-constrained systems, the the smem source includes a utility named smemcap. smemcap captures all /proc entries required by smem and outputs them as an uncompressed .tar file to STDOUT. smem can analyze the output using the --source option. smemcap is small and does not require Python.
    To use smemcap:
    1. Obtain the smem source at http://selenic.com/repo/smem
    2. Compile smemcap.c for your target system.
    3. Run smemcap on the target system and save the output: smemcap > memorycapture.tar
    4. Copy the output to another machine and run smem on it: smem -S memorycapture.tar

    配置config文件

  1. 配置kernel config
    linux/meson/axg_32/config-4.9
    CONFIG_PROC_PAGE_MONITOR=y
  2. 配置.config
    .config
    CONFIG_PROC_PAGE_MONITOR=y
    tips: .config配置会覆盖linux的config文件

参考链接


文章作者: Mr.Pan
版权声明: 本博客所有文章除特別声明外,均采用 CC BY 4.0 许可协议。转载请注明来源 Mr.Pan !
  目录