 | | | How much memory for SLES9 SP3 and Oracle 10.2.0.2 on 32 bits | How much memory for SLES9 SP3 and Oracle 10.2.0.2 on 32 bits 2006-11-27 - By Silviu Marin-Caea
Back
On Tuesday 14 March 2006 15:25, Magni Fabrizio wrote:
> Actually with the bigsmp kernel you can use up to 64GB of RAM and no
> "tricks" are needed.
>
> You will be still constrained by 4GB shared memory segments but this is
> not a real problem since you can allocate more than one.
>
> Even the SGA of an oracle 32bit is not constrained by 4GB.
I have been reading a lot of metalink documents on this. Some issues are
clear to me, others aren't. There is a lot of obsolete information to filter
out.
So far, what is clear is this:
SGA is made of "buffer cache" and "shared pool".
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.
The "shared pool" part will be allocated in regular memory (not ramfs). The
question is how much is the limit?
Also I've succeeded in creating HugePages and Oracle allocated memory in those
(all this on a test machine). If I understood correctly the HugePages are
required because the page table has a limited number of entries. Am I right?
The production servers have 16 GB and I have a test machine with 4 GB.
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting
|
|
|