Who knows, it’s like a black art, but one way is to use svmon. For example, find the PID of the suspect process and use
svmon -P [pid] -m |
This might give you something like:
-------------------------------------------------------------------------------
Pid Command Inuse Pin Pgsp Virtual 64-bit Mthrd 16MB
286902 java 1797187 8249 4657 1671072 Y Y N
PageSize Inuse Pin Pgsp Virtual
s 4 KB 1789587 8201 4657 1663472
m 64 KB 475 3 0 475 |
… lots of stuff snipped …
Add up Inuse, Pin, Pgsg and Virtual to get a figure. It won’t be exact, but might be relative enough for troubleshooting.
So, in this case, 1797187 + 8249 + 4657 + 1671072 = 3481165k = 3399.5M = 3.32G.
