Quote:
Originally Posted by
javanoob
Lastly, can i confirm the following one last time
Swap allocated will not be shown swap -l. swap used will be shown in swap -l.
"pages swapped out" and "pages swapped in" eventually ends as -> Current swap_used
No. What i meant was: a process gets (though whatever means,
mmap(),
shmget(), the OS or something else) space in the swap. This space will show up in
swap -l as "used". But from a performance POV you do not want to avoid "used swap", you want to avoid transferring memory pages to and from the swap because the actual act of transferring is what slows the system down. This "act of transferring" pages is either "page in" (a page transferred from swap to memory) or "page out" (a page transferred from emory to swap) and this shows in
vmstat. To extend jiliagres metaphor: if the restaurant in question serves unhealthy food, reserving the table there is not what gets you into trouble, only actually eating there is. So it doesn't help to look at the reservations to discern if someone is in danger or not.
Quote:
Originally Posted by
javanoob
Is there anyway to look into the physical swap area and see what's there and hold by which process ?
Now, this is a good question! I would refer you to the
ps command and - if you are really fearless - the
kdb (kernel debugger) command but the difference between me and jiliagre is that he is a Solaris expert and i am not. (Whatever i told you above is "general UNIX knowledge", not specialised Solaris knowledge). There is maybe some special Solaris way he is a aware of that i am not, so his word will be the last in this matter.
I hope this helps.
bakunin