RE: IDS 7.30 CPU Usage

I will mention some possible causes of your problems: 1) Have you run UPDATE STATISTICS against your tables in the manner recommended by the Release Notes? Failure to do so can cause performance problems. 2) Run the "onstat -P | tail -8" command. If a large percentage of your buffer pool pages are in-use by Btree indexes, you need to upgrade to a newer version which allows LRU priority to be disabled. Such releases are >= 7.30.UC10 or >= 7.31.UC4. 3) Are you running an OLTP application? If so, your LRU_MAX_DIRTY and LRU_MIN_DIRTY parameters may be set too high. This can lead to long checkpoints. Look at your online.log file for checkpoint durations. Lower values will cause dirty pages to be written via LRU writes between checkpoints. You can monitor write activity using "onstat -F". Many problems have been fixed since 7.30.UC5. Therefore, an upgrade would be recommended. We did not have much luck with 7.30.UC5 on our AIX systems. This led us to several subsequent upgrades. Good luck, Rick Bernstein -----Original Message----- From: Jay Turner [mailto:tjay@edcpub.com] Sent: Monday, December 27, 1999 2:00 PM To: informix-list@iiug.org Subject: IDS 7.30 CPU Usage Back in November we upgraded both our OS and Informix engine. From AIX 3.2.5 to AIX 4.3.2 and SE 5.03 UC1 to IDS 7.30 UC5. We are still using the same system (RISC 6000 59H 768 meg. memory) and programs (4gl programs recompiled with I4GL 7.20 UD6). We were told to expect a huge performance increase, well it hasn't happened. Actually as a whole it is slower, the problem appears to be that when we get a moderate amount of activity the online process starts taking up all the CPU resources making the whole system run slower. After studying several performance related articles, books, newsgroup posts and inquiring with other companies who have done something similar, we have come up with no solution. Does anyone have any suggestions? We really need to get this figured out. We are at a point where we need any help we can get and would be willing to pay someone to come to our location or help us remotely. Thanks for any help, Jay Turner Here is our onconfig file and a onstat profile. # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/raw_root # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 160000 # 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 12000 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 6 # Number of logical log files LOGSIZE 4000 # Logical log size (Kbytes) # Diagnostics MSGPATH /informix7/online.log # System message log file path CONSOLE /dev/console # System console message pathALARMPROGRAM /informix7/etc/log_full.sh # Alarm program path SYSALARMPROGRAM /informix7/etc/evidence.sh # System Alarm program path TBLSPACE_STATS 1 # System Archive Tape Device TAPEDEV /dev/rmt0 # Tape device path TAPEBLK 240 # Tape block size (Kbytes) TAPESIZE 7000000 # 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 Dynamic Server/Optical staging area # System Configuration SERVERNUM 0 # Unique id corresponding to a DynamicServer instance DBSERVERNAME prod1_srvr # Name of default database server DBSERVERALIASES # List of alternate dbservernames NETTYPE ipcshm,1,256,CPU # Configure poll thread(s) for nettype DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env. RESIDENT 0 # Forced residency flag (Yes = 1, No = 0) MULTIPROCESSOR 0 # 0 for single-processor, 1 formulti-processor NUMCPUVPS 1 # Number of user (cpu) vps SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps toone NOAGE 1 # Process aging AFF_SPROC 0 # Affinity start processor AFF_NPROCS 0 # Affinity number of processors # Shared Memory Parameters LOCKS 30000 # Maximum number of locks BUFFERS 24000 # Maximum number of shared buffers NUMAIOVPS 2 # 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 24 # Number of buffer cleaner processes SHMBASE 0x30000000 # Shared memory base address SHMVIRTSIZE 75000 # initial virtual shared memory segment size SHMADD 16000 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 600 # Check point interval (in sec) LRUS 24 # 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 markpercentage LTXEHWM 60 # Long transaction high water mark (exclusive) TXTIMEOUT 0x12c # Transaction timeout (in sec) STACKSIZE 32 # Stack size (Kbytes) # System Page Size # BUFFSIZE - Dynamic Server no longer supports this configuration parameter. # To determine the page size used by Dynamic Server 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 /informix7/etc/dr.lostfound #