Tuning Informix 7.2.4

Hi All, Can anyone take a look at the ONCONFIG file and the output of ONSTAT -P, ONSTAT -M and part of ONSTAT-G and make some tuning recommendations. This is running 7.2.4 on a Pyramid UNIX machine with 512M of memory, 4 CPUs and a 12K line password file (we know this might be a huge factor in the long wait times) .... That's about all I know about the system. Its taking 2-3 minutes to run applications with 10-20 users logged on and no other apps/databases running on the box. Thanks! Val #************************************************************************** # # INFORMIX SOFTWARE, INC. # # Title: onconfig.std # Description: INFORMIX-OnLine Configuration Parameters # #************************************************************************** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace name ROOTPATH /dev/dbtest11b # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 102400 # 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 12500 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 10 # Number of logical log files LOGSIZE 6250 # Logical log size (Kbytes) # Diagnostics MSGPATH /tras/informix.new/tras.new.log # System message log file path CONSOLE /dev/console # System console message path ALARMPROGRAM /tras/informix.new/etc/log_full.sh # Alarm program path TBLSPACE_STATS 1 # System Archive Tape Device TAPEDEV /dev/null # Tape device path TAPEBLK 16 # Tape block size (Kbytes) TAPESIZE 10240 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /dev/null # Log tape device path LTAPEBLK 16 # Log tape block size (Kbytes) LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes) # Optical STAGEBLOB # INFORMIX-OnLine/Optical staging area # System Configuration SERVERNUM 17 # Unique id corresponding to a OnLineinstance DBSERVERNAME natl_new # 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) MULTIPROCESSOR 1 # 0 for single-processor, 1 formulti-processor NUMCPUVPS 3 # Number of user (cpu) vps SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps toone NOAGE 0 # Process aging AFF_SPROC 0 # Affinity start processor AFF_NPROCS 0 # Affinity number of processors # Shared Memory Parameters LOCKS 15000 # Maximum number of locks BUFFERS 75000 # Maximum number of shared buffers NUMAIOVPS 6 # Number of IO vps PHYSBUFF 32 # Physical log buffer size (Kbytes) LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 30 # Maximum number of logical log files CLEANERS 8 # Number of buffer cleaner processes SHMBASE 0x20000000 # Shared memory base address SHMVIRTSIZE 8000 # initial virtual shared memory segment size SHMADD 8192 # 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 queues LRU_MAX_DIRTY 70 # LRU percent dirty begin cleaning limit LRU_MIN_DIRTY 30 # LRU percent dirty end cleaning limit LTXHWM 50 # Long transaction high water markpercentage LTXEHWM 60 # Long transaction high water mark (exclusive) TXTIMEOUT 0x12c # Transaction timeout (in sec) STACKSIZE 32 # Stack size (Kbytes) # 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 10 # Default number of offline workerthreads ON_RECVRY_THREADS 1 # Default number of online worker threads # Data Replication Variables # DRAUTO: 0 manual, 1 retain type, 2 reverse type DRAUTO 0 # DR automatic switchover DRINTERVAL 30 # DR max time between DR buffer flushes (in sec) DRTIMEOUT 30 # DR network timeout (in sec) DRLOSTFOUND /tras/informix.new/etc/dr.lostfound # DR lost+found filepath # CDR Variables CDR_LOGBUFFERS 2048 # size of log reading buffer pool (Kbytes) CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional) CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds) CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue (Kbytes) # Backup/Restore variables BAR_ACT_LOG /tmp/bar_act.log BAR_MAX_BACKUP 0 BAR_RETRY 1 BAR_NB_XPORT_COUNT 10 BAR_XFER_BUF_SIZE 31 # Read Ahead Variables RA_PAGES # Number of pages to attempt to read ahead RA_THRESHOLD # 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 dbtemp1 # 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 DUMPSHMEM 1 # Dump a copy of shared memory DUMPGCORE 0 # Dump a core image using

Webber Valerie H wrote: > > Hi All, > > Can anyone take a look at the ONCONFIG file and the output of ONSTAT -P, > ONSTAT -M and part of ONSTAT-G and make some tuning recommendations. This is > running 7.2.4 on a Pyramid UNIX machine with 512M of memory, 4 CPUs and a > 12K line password file (we know this might be a huge factor in the long wait > times) .... That's about all I know about the system. Its taking 2-3 > minutes to run applications with 10-20 users logged on and no other > apps/databases running on the box. [SNIP] Valerie, The onstat -c, config file listing, looks fine in a vacuum, the only thing is with 20 users 8 LRUs MAY be tight. Also a runtime of 2-3 minutes is not neccessarily slow. What do those apps have to do that should be faster? Ie table structure and query type at least at an overview level would help. In addition the onstat -p and onstat -m are not very helpful since the engine was not online log enough for decent stats to be posted. Post stats covering 1-2 days for onstat -p, -g ioq, -g iov, -g iof, -F, & -l, -g dsc. From the limited stats you posted I can only see that there are a relatively large number of sequential scans given the limited number of pages read into the buffer cache. Otherwise I cannot tell that anything is wrong. Art S. Kagel