Re: System is slow ...
From: Shahid Mehmood <theixdba@yahoo.com>
>
>OS: SCO UNIX -- OPEN SERVER 5.0
>IX: OWS 7.20.UC2
>
>I have one box with OWS installed on it. This instance
>contains 4 dbspaces, and 4 respective databases. All
>the users connect to their respective databases
>through application written using Informix 4GL (c-code
>version). The users are complaining that the system
>response is slow.
>
>Any suggestions, as how to improve the performance? I
>am waiting anxiously for your valueable replies, and
>comments.
>
>Thanks.
>
>My onconfig.ows file is as follows:
>
>$ cat onconfig.ows
>#**************************************************************************
>#># INFORMIX SOFTWARE, INC.
>#
># Title: onconfig.ows
># Description: INFORMIX-OnLine Configuration
>Parameters
>#
>#**************************************************************************
>
># Root Dbspace Configuration
>
>ROOTNAME rootdbs # Root dbspace name
>ROOTPATH /u/IFMXDATA/AKU/ROOTDBS.000
>ROOTOFFSET 0 # Offset of root>dbspace into device (Kbytes)
>ROOTSIZE 20000 # Size of root dbspace
>(Kbytes)>
># Disk Mirroring Configuration Parameters
>
>MIRROR 0 # Mirroring flag (Yes = 1,
>No = 0)
>MIRRORPATH
>MIRROROFFSET 0 # Offset into mirrored
>device (Kbytes)>
># Physical Log Configuration
>
>PHYSDBS rootdbs # Location (dbspace)
>of physical log
>PHYSFILE 2000 # Physical log file
>size (Kbytes)
Move your physical log to it's own dbspace, on it's own spindle.
># Logical Log Configuration
>
>LOGFILES 6 # Number of logical>log files
>LOGSIZE 1000 # Logical log size
>(Kbytes)>
># Diagnostics
>
>MSGPATH /u/usr/informix/etc/online.log #
>System message log file path
>CONSOLE /dev/console # System console>message path
>ALARMPROGRAM /u/usr/informix/etc/log_full.sh #
>Alarm program path
>
># System Archive Tape Device
>
>TAPEDEV /dev/rStp0
>TAPEBLK 16 # Tape block size
>(Kbytes)
>TAPESIZE 4000000 # Maximum amount of>data to put on tape (Kbytes)
>
># Log Archive Tape Device
>
>LTAPEDEV /dev/null
>LTAPEBLK 16 # Log tape block size
>(Kbytes)
>LTAPESIZE 10240 # Max amount of data>to put on log tape (Kbytes)
/dev/null? Bit brave.
># Optical
>
>STAGEBLOB #
>INFORMIX-OnLine/Optical staging area
>
># System Configuration
>
>SERVERNUM 0 # Unique id>corresponding to a OnLine instance
>DBSERVERNAME AKU # Name of default database>server
>DBSERVERALIASES AKU_shm # List of alternate>dbservernames
>NETTYPE tlitcp,1,,
>NETTYPE ipcshm,1,,
>DEADLOCK_TIMEOUT 60 # Max time to wait of>lock in distributed env.
>RESIDENT 0 # Forced residency
>flag (Yes = 1, No = 0)
Try 1 or -1
>MULTIPROCESSOR 0 # 0 for>single-processor, 1 for multi-processor
>NUMCPUVPS 1 # Number of user (cpu)>vps
>SINGLE_CPU_VP 0 # If non-zero, limit>number of cpu vps to one
>
>NOAGE 0 # Process aging
>AFF_SPROC 0 # Affinity start>processor
>AFF_NPROCS 0 # Affinity number of>processors
>
># Shared Memory Parameters
>
>LOCKS 2000 # Maximum number of>locks
>BUFFERS 200 # Maximum number of>shared buffers
You *definitely* need more BUFFERS. What's the hardware spec?
>NUMAIOVPS # Number of IO vps
>PHYSBUFF 32 # Physical log buffer
>size (Kbytes)
>LOGBUFF 32 # Logical log buffer
>size (Kbytes)>LOGSMAX 6 # Maximum number of
>logical log files
>CLEANERS 1 # Number of buffer>cleaner processes
Try 8.
>SHMBASE 0x10000000L # 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 60 # LRU percent dirty>begin cleaning limit
>LRU_MIN_DIRTY 50 # LRU percent dirty>end cleaning limit
>LTXHWM 50 # Long transaction>high water mark percentage
>LTXEHWM 60 # Long transaction>high water mark (exclusive)
>TXTIMEOUT 300 # 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 worker threads
>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 /usr/informix/etc/dr.lostfound # DR>lost+found file path
>
># 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 # 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 # Preser