Re: Fighting Words? Shared Pool Size

Ross,

cursor_space_for_time will nearly always end up with a large shared pool. As to what defines a large shared pool depends heavily on the number of applications that the instance has to support. After sizing exercises, I've ended up with Shared Pools ranging from about 20Mb's upto about 400Mb's. Both were about the correct size for the job they were being asked to perform.

I think the important thing is that you don't see to much stealing of space from one object class (library cache, dictionary cache, sql area) to fund another. Keep an eye on the v$sgastat output over the course of time.

Andrew

Ross Mohan wrote:

> I say the shared pool should never get "too big", that it was never
> designed to be 250MB, or 2G.
>
> I am resolving a severe latch-based perf problem by shrinking the
> pool and *removing* cursor_space_for_time, and of course, pinning.
>
> Any vehement objections?
Received on Mon Apr 19 1999 - 23:13:14 CDT