I assume bgdak has been looking at the available(free) memory in swapinfo.
HP's buffer cache is only dynamic one way, up. It's been that way since 10.01. (oh, and going to be fixed since then as well)
I have seen this many times on quiet systems. 60% utilized = 50% taken by the buffer cache and 10% by the OS and remainder little stuff running.
run this command
echo bufpages/D | adb /stand/vmunix /dev/kmem
You'll get this
bufpages:
bufpages: 13107 --- your number
That's the number of 4k pages of buffer cache real time.
Then use bc and 13107*4096/1024/1024 = 51MB <-- Your number is????
Now, I am not saying change it. It depends on what the applications are -- Oracle: best practice is to run at 5% and 10% but say Universe DB: it needs to stay as high as possible (Oracle caches on it's own Universe does not).
Mike - You are absolutly correct about the swap information not changing.
However IF the buffer cache is not shrinking dynamically, and you were to change dbc_max_pct down the memory utilization would go down -- BUT the mem and dev swap would remain the same.
STF