If the shared pool has free memory (except just after instance start-up) then it
is certainly too big. The shared pool is a cache and should normally be almost
completely full. The large pool is not a cache. The large pool should be sized
according to the high-water mark of large pool memory usage.


-----Original Message-----
Sent: Thursday, 31 August 2000 0:04


In your previous answer you wrote: "If V$SGASTAT always shows plenty of
'free memory' then its too big".
In Gurry & Corrigan's "Oracle Performance Tuning" I've read the same about
monitoring of size of the shared pool. Could you tell me please the approx.
lower size of free memory for large/shared pool when you would be consider
it as plenty (superfluous). I'm not sure this is the correct question. Maybe
the more exact question is  What the portion of shared/large pool's memory I
should consider as superfluous when it's free?