1 The following is a demonstration of the anonpgpid.d script,
4 Here we run it on a system that is implementing memory caps using the
5 resource capping daemon, "rcapd",
8 Tracing... Hit Ctrl-C to end.
14 6222 memleak.pl R 974848
15 6222 memleak.pl W 3055616
17 The "memleak.pl" process consumes memory, and we can see above that it has
18 encountered both reads and writes to the physical swap device - it is being
19 paged out. A bash shell was also effected (which was in the same project that
20 rcapd was monitoring).
24 The following is an ordinary system that is very low on memory,
27 Tracing... Hit Ctrl-C to end.
31 18600 automountd R 4096
45 165 in.routed R 131072
46 294 automountd R 135168
50 7 svc.startd R 1015808
51 9 svc.configd R 1478656
54 The "pageout" process is responsible for writing all the anonymous memory
55 pages to the physical swap device, and we can see from the above that it
56 has written 23 Mb. When processes access anonymous memory that has been
57 swapped out, a major fault occurs and the memory is paged back in; in this
58 case we can trace the process that was effected, and from the above we can
59 see that several processes have been effected by the memory pressure.
60 The most is "svc.configd", which needed to page back in 1.4 Mb of anonymous
65 Sometimes anonpgpid.d doesn't help too much. Here we only have pageouts
66 to the physical swap device and no pageins,
73 Only pageout is identified.