Re: size sga

Hi:

All the physical memory in your server is shared by different processes; the key of performance turning is balance your resource to different requirements. the indicators of your SGA size is big enough are data buffer cache hit ratio (> 90%) and library cache hit ratio (
>95%);

you can adjust your SGA size base on them; as long as cache hit ratio is
in the idea range; you should release unnecessary memory from SGA back to OS and focus on other turning categories.

Regards,
JEFF Xu

In article <37F477D1.79E82809_at_totalise.co.uk>,   Martin Hepworth <maxsec_at_totalise.co.uk> wrote:
> nieuws net wrote:
> >
> > Hi all
> >
> > we have a NT server with 1 GIGA RAM
> > oracle version 7.3.4
> >
> > DB_BLOCK_SIZE = 4096
> >
> > i set db_block_buffers = 50000 (200Mb)
> > shared_pool_size = 300000000 (300Mb)
> > so oracle SGA claims approx 500Mb from the total of 1 GIG
> > However the performance is dramatic(performance lose of more than 20
> > seconds)
> >
> > When i decrease db_block_buffers to 10000 (40M)
> > and shared_pool_size to 9000000 (9M) , then the performance is
acceptable.
> >
> > Any idea how this is possible ?
> >
> > Many thanks
> > gkor_at_rdw.nl
>
> Hi
> theres some specific stuff on NT/Oracle tuning at
> http://www.ipass.net/~davesisk/oont.htm
>
> You could also try putting 'lock_sga=TRUE' in the init.ora for the db
to
> stop NT PAging the SGA out.
>
> Also make sure you've the NT setup to be a network app server not a
> fileserver (see the URL for details).
>
> martin
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Fri Oct 01 1999 - 15:34:48 CDT