Re: OnConfig parameters tuning

Laverio wrote: > Hi guys, I'm trying to speed up an IDS 9.30 on a Sun 7.5 system w/ 2Gb ram > and 4 processors that seems very slow on a large sequential write (I suppose > that the problem resides in the dbspaces on filesystem...). Any suggestion? > > My onconfig it's set as follow: > The $ONCONFIG is one thing, but some information from the instance / O/S / usage / expectations / load on machine / etc. etc. would be some of the other things needed to really provide some decent tuning suggestions however ... > # System Configuration > > SERVERNUM 0 # Unique id corresponding to a OnLine> instance > DBSERVERNAME sbn # Name of default database server > DBSERVERALIASES sbn_tcp # List of alternate dbservernames > DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed > env. > RESIDENT 0 # Forced residency flag (Yes = 1, No = 0) > > MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 4 # Number of user (cpu) vps Limit to 1, give the O/S some :) > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to> one > > NOAGE 0 # Process agingSet to 1, don't let the O/S bring ya down in priority > AFF_SPROC 0 # Affinity start processor > AFF_NPROCS 0 # Affinity number of processors> > # Shared Memory Parameters > > LOCKS 120000 # Maximum number of locks > BUFFERS 262144 # Maximum number of shared buffers512Mb of buffers, can ya give any more?? Depends on what else is on your machine. > NUMAIOVPS # Number of IO vpsHumm, blank entry is bad, specify a number (something like Number of "active" chunks to start with and then search on this newsgroup for I/O stuff) > PHYSBUFF 64 # Physical log buffer size (Kbytes) > LOGBUFF 64 # Logical log buffer size (Kbytes) > CLEANERS 1 # Number of buffer cleaner processesHumm, 1 is ... low, increase to what you have increased NUMAIOVPs to to start with > SHMBASE 0x0A000000L # Shared memory base address > SHMVIRTSIZE 8000 # initial virtual shared memory segment sizeHumm, seems low, check onstat -g seg, add all the ones with a V type, and increase this value to that. > SHMADD 32768 # Size of new shared memory segments (Kbytes) > SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited > CKPTINTVL 300 # Check point interval (in sec) > LRUS 8 # Number of LRU queuesHumm, OLTP vs MIS - OLTP - with BUFFERS set to 512MB suggest 65, for MIS suggest 17 > LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit > LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limitWhoa there Lesley, if you care about checkpoint duraction, take this down to 4 / 2 (i.e. 4% of 512Mb of BUFFERS is about 8Mb; should be able to clear in under a second or two. > TXTIMEOUT 0x12c # Transaction timeout (in sec) > STACKSIZE 64 # Stack size (Kbytes)> BUT ... you should test this first :)