My biggest concern has been more making sure that Oracle doesn't have to fight
to get memory, which it does now. There's definite performance uptick during
the process of releasing ARC cache memory to allow Oracle to get what it's
asking for and this is passed on to the application. The problem
On Mar 16, 2007, at 1:29 PM, JS wrote:
I've been seeing this failure to cap on a number of (Solaris 10
update 2 and 3) machines since the script came out (arc hogging is
a huge problem for me, esp on Oracle). This is probably a red
herring, but my v490 testbed seemed to actually cap on 3 s
> I've been seeing this failure to cap on a number of (Solaris 10 update
> 2 and 3) machines since the script came out (arc hogging is a huge
> problem for me, esp on Oracle). This is probably a red herring, but my
> v490 testbed seemed to actually cap on 3 separate tests, but my t2000
> testbed do
I've been seeing this failure to cap on a number of (Solaris 10 update 2 and 3)
machines since the script came out (arc hogging is a huge problem for me, esp
on Oracle). This is probably a red herring, but my v490 testbed seemed to
actually cap on 3 separate tests, but my t2000 testbed doesn't e
