Re: Shared Memory Segments on Solaris 2.5.1

Martin Hepworth <maxsec_at_totalise.co.uk> writes:

> Basically setting arbitarily large values has little impact on the
> performance of the system, but its an issue when you've maxed out in the
> db_block_buffers/shared_pool_size in Oracle and you have to edit
> /etc/system and reboot, rather than just edit init.ora to your hearts
> content.

As far as I know there's no penalty for large values of shmmax either, we have it set nearly as high as you :)

set shmsys:shminfo_shmmax=1073741824
set semsys:seminfo_semmap=10240
set semsys:seminfo_semmns=8192
set semsys:seminfo_semmni=32
set semsys:seminfo_semmsl=256
set semsys:seminfo_semmnu=32
set semsys:seminfo_semopm=32
set semsys:seminfo_semume=32

But your values from some of the semaphore parameters seem a little odd to me. semmns is the total number of semaphores in the system, having it less than semmsl which is semaphores per segment is weird, in fact I think it should be equal to semmni*semmsl.

> set shmsys:shminfo_shmmax=4294967295
> set shmsys:shminfo_shmmin=1
> set shmsys:shminfo_shmmni=1024
> set shmsys:shminfo_shmseg=1024
> set semsys:seminfo_semmap=1002
> set semsys:seminfo_semmni=500
> set semsys:seminfo_semmns=400
> set semsys:seminfo_semmnu=500
> set semsys:seminfo_semmsl=500
> set semsys:seminfo_semopm=100
> set semsys:seminfo_semume=100
> set semsys:seminfo_semusz=256
> set semsys:seminfo_semvmx=32767
> set semsys:seminfo_semaem=16384

--
greg Received on Fri Nov 05 1999 - 18:25:50 CST