On Monday 27 November 2006 12:37, you wrote:
> Silviu Marin-Caea schrieb:
> > On Monday 27 November 2006 10:46, you wrote:
> >> Silviu Marin-Caea schrieb:
> >>> So far, what is clear is this:
> >>>
> >>> SGA is made of "buffer cache" and "shared pool".
> >>
> >> Correct.
> >>
> >>> The "buffer cache" part can be put on ramfs if Oracle uses VLM.
> >>> Therefore the buffer cache can be made very large, for example 6 GB.
> >>
> >> Yes.
> >>
> >>> The "shared pool" part will be allocated in regular memory (not ramfs).
> >>> The question is how much is the limit?
> >>
> >> On 32-bit approx. 1,7 GB; if you lower the mapped base approx. 2,7 GB.
> >
> > Therefore the stuff about lowering the mapped base still applies? I've
> > been kind of skipping over that because it was always in sections
> > applying to Red Hat 2.1.
>
> Well, i would do it if you really need a shared pool of > 1.7 GB. If not
> - dont do it....

Out of those 1.7 GB we have to count out 0.5 GB to manage the VLM, therefore
the actual remaining size for shared pool would be 1.2 GB.

So, the trick with the mapped base still applies to SLES9 SP3 w/updates? Is
it worth the effort of understanding? Or is it obsolete? In other words,
can it be done, no matter how hard it is?


--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting