Raising these parameters will have a direct effect on the amount of memory
allocated to the SGA hense you saw free memory go down. These parameters
are key to performance tuning on a system.
shared_pool_size is the amount of memory availiable for user sql,
procedures etc to reside in, the more you have the more you can store in
memory.
db_block_buffers is the amount os memory available to cache data blocks.
the more blocks you can cache the less likely it is to perform an IO to
disk to get the data block.
log_buffers is the amount of memory available to store redo log
transactions. the more you have the less frequent you will have to write to
the redo logs, again reducing IO.
Phil Hoggins,
SEQUENT COMPUTER SYSTEMS.
Ed Lufker <elufker_at_swcp.com> wrote in article
<6h1hor$jfp$1_at_sloth.swcp.com>...
> Hi All:
>
>
> Could someone please tell me what happens when you adjust the
> following parmeters;
>
> shared_pool_size = 1000000000
> db_block_buffers = 61000
> log_buffers = 102400
>
> I changed db_block_buffers from 60000 to 61000, hoping to get more
buffers
> for storing tables and indexes in memory, was this the right thing to do?
>
> What areas get affected?? I noticed that when I upped the
> db_block_buffers, the free memory went down, what does that mean. Will my
> users suffer, the free memory went down to 90Meg.
>
> thanks
> eddie lufker
>
Received on Wed Apr 15 1998 - 08:51:50 CDT
