Currently I'm experience very high page ins on my system running on solaris 10.
From vmstat, the page ins figure is very high, further drill down shows the page ins are from file system and occassional spike in executable page ins.
So, for example, you have 13,209,752,927,129 page-in's in a 5 second period? That's a little bit more powerful than the systems I work with. Please tell us about your system. It's gotta be ccNUMA, but how many cpu's?
Well, since you have enough disks to supply 2.6 quadrillion pages in a second, you can afford some more swap space. So just add a few TB more swap.
I'm trying to look at why the swap space is being consumed consistently, and it isn't released back to the system. At this rate, it's just a matter of time the swap goes out again. Our bomb just exploded just week, and bring our oracle instance down due to out of /tmp forcing a restart of the instance which releases the memory.
Actually I was trying to be facetious. Numbers like that make me think that vmstat must be broken. If I ignore the pi and assume that the rest of the numbers are valid, I don't really see any problem. You have swap and free physical memory. Page-outs are low and so is the scan rate. So pi is impossible and everything else looks good. I guess I would look for a vmstat patch though.
But if swap is disappearing, do a "df -k". /tmp uses swap for sure and I think maybe /var/run or something like that does as well. Could /tmp be eating your swap area? If it's a program, the size as reported by ps would be growing over time. Also I often see people over-allocate shared memory to Oracle. So when Oracle is running I do a "ipcs -mb" to look at that.
yea, that's what I'm looking at currently too. Vxfs 4.1 bug.
@reborg, it's running on vxfs. which may trigger the the high pi bogus numbers.
I have another concern is the disappearing swap space. I can see clearly that the free swap space is dropping by the day, but unable to nail down the culprit. any suggestion how should I approach it?
You're looking for large processes. And you want to save the output. Run it each day. Compare all of the outputs and see if anything growing over time. You probably have a classic memory leak.