Re: onconfig recommendations

On Jan 2, 11:09 pm, "Kennedy, Randy" <RKenn...@scottsdaleaz.gov> wrote: > Would like to receive some feedback on our onconfig setup for current > platform. This is the 3rd physical server that the database has moved > to and just want to ensure we are using the best settings for given > platform. > > Current Server: HP rp5405 4-Way (650 MHz) with 8GB RAM. 1 73GB hard > drive (4 drives installed, but sysadmin took 2 for O/S, system and other > 2 are mirrored pair so effectively 1 spindle to work with). I didn't > get to specify the configuration. > > Old Server: HP something 4 way with 4GB RAM. 5 spindles to work with. > > When moved to current server, I did up thebuffersand locks. > We use ontape for Level 0 and logical log backups. They are done via > files and links to remote server instead of actual tape. > > System is primarily OLTP with some batch jobs run overnight (off > business hours). > > Any insight will be appreciated. Please let me know if you would like > any other information. > > TIA, > Randy > > # Root Dbspace Configuration > ROOTNAME rootdbs # Root dbspace name > ROOTPATH /db/links/rootdbs # Path for device containing root> dbspace > ROOTOFFSET 0 # Offset of root dbspace into device > (Kbytes) > ROOTSIZE 384000 # Size of root dbspace (Kbytes)> > # Disk Mirroring Configuration Parameters > MIRROR 0 # Mirroring flag (Yes = 1, No = 0) > MIRRORPATH # Path for device containing mirrored> root > MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> > # Physical Log Configuration > PHYSDBS rootdbs # Location (dbspace) of physical log > PHYSFILE 60000 # Physical log file size (Kbytes)> > # Logical Log Configuration > LOGFILES 85 # Number of logical log files > LOGSIZE 12000 # Logical log size (Kbytes) > LOG_BACKUP_MODE CONT> > # Diagnostics > MSGPATH /i9.4/informix/online.log # System message log file path > CONSOLE /dev/console # System console message path > ALARMPROGRAM /db/scripts/no_log.sh # Alarm program path> > # System Archive Tape Device > #TAPEDEV /dev/rmt/2m # Tape device path > TAPEDEV /remote/recovery/informix/level0 # Tape device path > TAPEBLK 16 # Tape block size (Kbytes) > TAPESIZE 30000000 # Maximum amount of data to put on tape > (Kbytes)> > # Log Archive Tape Device > #LTAPEDEV /dev/rmt/2m # Log tape device path > LTAPEDEV /ltape1/informix/log1 # Log tape device path > LTAPEBLK 16 # Log tape block size (Kbytes) > LTAPESIZE 4500000 # Max amount of data to put on log tape > (Kbytes)> > # Optical > STAGEBLOB #INFORMIX-OnLine/Optical staging area > > # System Configuration > SERVERNUM 0 # Unique id corresponding to a OnLine> instance > DBSERVERNAME courtshm # Name of default database server > DBSERVERALIASES # 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) > NETTYPE soctcp,4,150,NET > NETTYPE ipcshm,1,25,NET > MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 16 # Number of user (cpu) vps > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps> to one > NOAGE 1 # Process aging > AFF_SPROC 0 # Affinity start processor > AFF_NPROCS 0 # Affinity number of processors> > # Shared Memory Parameters > LOCKS 80000 # Maximum number of locksBUFFERS 150000 # Maximum number of sharedbuffers > NUMAIOVPS 26 # Number of IO vps > PHYSBUFF 64 # Physical log buffer size (Kbytes) > LOGBUFF 32 # Logical log buffer size (Kbytes) > CLEANERS 28 # Number of buffer cleaner processes > SHMBASE 0x0 # Shared memory base address > SHMVIRTSIZE 160000 # initial virtual shared memory segment> size > SHMADD 80000 # Size of new shared memory segments > (Kbytes) > SHMTOTAL 0 # Total shared memory (Kbytes). > 0=>unlimited > CKPTINTVL 300 # Check point interval (in sec) > LRUS 20 # Number of LRU queues > LRU_MAX_DIRTY 5.000000 # LRU percent dirty begin cleaning limit > LRU_MIN_DIRTY 2.000000 # LRU percent dirty end cleaning limit > LTXHWM 50 # Long transaction high water mark> percentage > LTXEHWM 60 # Long transaction high water mark > (exclusive) > TXTIMEOUT 0x12c # Transaction timeout (in sec) > STACKSIZE 64 # Stack size (Kbytes) > PC_POOLSIZE 110 # Stored Procedures Cache> > # System Page Size > # BUFFSIZE - OnLine no longer supports this configuration parameter. > # To determine the page size used by OnLine on your platform > # see the last line of output from the command, 'onstat -b'. > > # Recovery Variables > # OFF_RECVRY_THREADS: > # Number of parallel worker threads during fast recovery or an offline > restore. > # ON_RECVRY_THREADS: > > # Number of parallel worker threads during an online restore. > OFF_RECVRY_THREADS 15 # Default number of offline worker> threads > ON_RECVRY_THREADS 15 # Default number of online worker> threads > > # Data Replication Variables > # DRAUTO: 0 manual, 1 retain type, 2 reverse type > DRINTERVAL 30 # DR max time between DR buffer flushes > (in sec) > DRTIMEOUT 30 # DR network timeout (in sec)> DRLOSTFOUND /usr/informix/etc/dr.lostfound # DR lost+found file path > > # Read Ahead Variables > RA_PAGES 64 # Number of pages to attempt to read> ahead > RA_THRESHOLD 8 # Number of pages left before next group> > # DBSPACETEMP: > # OnLine equivalent of DBTEMP for SE. This is the list of dbspaces > # that the OnLine SQL Engine will use to create temp tables etc. > # If specified it must be a colon separated list of dbspaces that exist > # when the OnLine system is brought online. If not specified, or if > # all dbspaces specified are invalid, various ad hoc queries will create > # temporary files in /tmp instead. > DBSPACETEMP tempdbs1,tempdbs2,tempdbs3,tempdbs4 # Default temp > dbspaces > > # DUMP*: > # The following parameters control the type of diagnostics information > which > # is preserved when an unanticipated error condition (assertion failure) > occurs > # during OnLine operations. > # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No. > DUMPDIR /tmp # Preserve diagnostics in this directory> DUMPSHME

> Hey Randy, > > some recommendations for you. > > > TAPEBLK 16 # Tape block size (Kbytes)> > would try 128 oder 256, it can reduce your backup time. > > > TAPESIZE 30000000 # Maximum amount of data to put on tape> > with 9.4 its possible to set the tapesize parameter to 0, so its use > the whole place from the tape or device, so its not necessary to > adjust the parameter in the future > > > NUMCPUVPS 16 # Number of user (cpu) vps> > you should set this parameter #CPU * Cores - 1, when you dont have > other applications on this server > > > LOCKS 80000 # Maximum number of locks> > you did up the locks, but this is only necessary when you have > problems with lock overflows, however, the informix engine adds 100000 > locks on the fly for eight times when its necessary, so you have > 880000 possible locks in the system. you have a lot of ram, you can > increase it, no problem, 1 locks needs 4 bytes. > > > BUFFERS 150000 # Maximum number of shared buffers> > this server is only a database server, no other applications? then you > should increase buffers up to 30-50% of the physical ram. when you > change the bufferpool size you should adjust the SHMVIRTSIZE. > With more buffers the checkpoint duration can be higher, so you should > decrease LRUMAX and MIN to 2 and 1 > > > NUMAIOVPS 26 # Number of IO vps> > i think hpux works with kio, this paramater is not so important, you > can set this parameter to nothing, the engine starts then with 2 AIO > VPS per chunk > > > CLEANERS 28 # Number of buffer cleaner processes > > LRUS 20 # Number of LRU queues> > cleaners and lrus should be equal. > > no warranty ;-) > > Sebastian 44bytes per lock on 32bit and 96bytes per lock on 64 bit, sorry, my mistake thx to Art S. Kagel Sebastian