[pypy-svn] r57900 - pypy/branch/cross-compilation/pypy/doc/discussion

[fijal at codespeak.net]

Author: fijal
Date: Sat Sep  6 19:47:37 2008
New Revision: 57900

Modified:
   pypy/branch/cross-compilation/pypy/doc/discussion/gc-memory-notes.txt
Log:
Notes how to read smaps


Modified: pypy/branch/cross-compilation/pypy/doc/discussion/gc-memory-notes.txt
==============================================================================
--- pypy/branch/cross-compilation/pypy/doc/discussion/gc-memory-notes.txt	(original)
+++ pypy/branch/cross-compilation/pypy/doc/discussion/gc-memory-notes.txt	Sat Sep  6 19:47:37 2008
@@ -28,3 +28,21 @@
 
 I think we need some kind of graph which shows how exactly this grows with
 number of objects.
+
+Some notes how to read memory footprint on linux:
+
+all stuff that we want to know is located in /proc/$pid/smaps (beginning
+from linux 2.6.16, which is almost any apparently). This contains:
+Size, Rss, Shared and Private. Note that all addresses are virtual, which means
+that having the same address in two processes doesn't mean it's the same memory.
+
+Explanation:
+Size: total (virtual) size of memory, possibly irrelevant
+Rss: real size of memory
+Shared: memory shared with other processes. Note that this is simply a counter
+how many processes reference it. Memory can move private -> shared in case
+some other process will load the same library or so.
+Private: private memory owned by a process.
+
+Distinction clean/dirty is related to swap and probably irrelevant to our
+measurments.