[dtrace-discuss] Re: How to trace process memory usage

[Peter Eriksson]

> prstat(1) is your friend. "prstat -s rss" is a wonderfully simple and effective

There is only one small problem with that approach - when things are running normally we don't see any strange behaviour. And when things misbehave we typically can't start any new processes (fork: resource temporarily unavailable)...
Ie, no prstat/vmstat/pmap/top/ps..

That's why we was thinking of using an already running Dtrace to try to "see" what's going on when things are misbehaving...


Anyway, I've now increased the available swapspace so it's more than the size of the RAM in the machine and we'll see what happens...
 
 
This message posted from opensolaris.org