Informix/Baan/AIX Performance

We are experiencing performance issues since upgrading to AIX 4.3.3 from 4.3.2. The Informix database configuration has not changed and all the latest patches/fixes have been applied to the OS. We are running on a AIX4.3.3 / Informix7.31.UC3X1 / BAAN4C3(level 1 driver) environment. We have also noted that when the onbar backups run (particularly level 0) we see checkpoints as high as 30 minutes. Any help / suggestions would be greatly appreciated. I can supply any other necessary info if requested. Thanks, Andy We have an S7A 12 cpu / 6 gig / ssa striped and OS mirrored. We also run Baan on this server for batch jobs. All the users are tcp GUI Baan clients (rexec). A typical "sar 5 5" shows: 11:37:22 %usr %sys %wio %idle 11:37:27 8 21 0 71 11:37:32 9 21 0 70 11:37:37 9 21 0 69 11:37:42 7 20 0 73 11:37:47 9 21 0 70 Average 9 21 0 71 =========================================================================== Provided below are the onconfig, onstat -g mgm, onstat -g iov, sqlhosts =========================================================================== ONCONFIG =========================================================================== #************************************************************************** # # INFORMIX SOFTWARE, INC. # # Title: onconfig.baansv01 for 7.31.UC3X1 # Description: Informix Dynamic Server Configuration Parameters # #************************************************************************** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace nameROOTPATH /usr/Informix/links/Infmx400Root # containing root dbspace ROOTOFFSET 64 # Offset of root dbspace into device (Kbytes) ROOTSIZE 350000 # Size of root dbspace (Kbytes) # Disk Mirroring Configuration Parameters MIRROR 1 # Mirroring flag (Yes = 1, No = 0) MIRRORPATH # device containing mirrored root MIRROROFFSET 0 # Offset into mirrored device # Physical Log Configuration PHYSDBS physdbs # Location (dbspace) of physical log PHYSFILE 699788 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 81 # Number of logical log files LOGSIZE 5000 # Logical log size (Kbytes) # Diagnostics MSGPATH /usr/Informix/online.log # System message log file path CONSOLE /usr/Informix/console.log # console message path ALARMPROGRAM /usr/Informix/etc/log_full.sh # Alarm program path SYSALARMPROGRAM /usr/Informix/etc/evidence.sh # System Alarm program path # TBLSPACE_STATS 1 # System Archive Tape Device TAPEDEV /dev/rmt0 # Tape device path#TAPEDEV /dev/null # Tape device path TAPEBLK 512 # Tape block size (Kbytes) TAPESIZE 10000000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /dev/rmt0 # Log tape device path#LTAPEDEV /dev/null # Log tape device path LTAPEBLK 512 # Log tape block size (Kbytes) LTAPESIZE 8000000 # Max amount of data to put on log tape (Kbytes) # Optical STAGEBLOB # Informix Dynamic Server/Optical staging area # System Configuration SERVERNUM 1 # Unique id corresponding to a DynamicServer instance DBSERVERNAME baan01b # Name of default database serverDBSERVERALIASES baansv01,baansv01_str,baansv01_shm # List of alternate dbservernames NETTYPE ipcstr,1,40,NET # Configure poll thread(s) for nettype NETTYPE ipcshm,1,40,CPU # Configure poll thread(s) for nettype NETTYPE soctcp,2,300,NET # Configure poll thread(s) for nettype NETTYPE sqlmux,1,20,NET # 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 1 # 0 for single-processor, 1 formulti-processor NUMCPUVPS 10 # Number of user (cpu) vps SINGLE_CPU_VP 0 # 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 DD_HASHSIZE 211 # Number of HASH buckets for Data Dictionary DD_HASHMAX 40 # Number of entries in each DD HASH bucket LOCKS 2500000 # Maximum number of locks BUFFERS 135000 # Maximum number of shared buffers NUMAIOVPS 2 # Number of IO vps PHYSBUFF 256 # Physical log buffer size (Kbytes)#LOGBUFF 32 # Logical log buffer size (Kbytes) LOGBUFF 64 # Logical log buffer size (Kbytes)LOGSMAX 150 # Maximum number of logical log files CLEANERS 128 # Number of buffer cleaner processes SHMBASE 0x30000000L # Shared memory base address SHMVIRTSIZE 1548576 # initial virtual shared memory segment size SHMADD 65536 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 300 # Check point interval (in sec) LRUS 128 # Number of LRU queues LRU_MAX_DIRTY 1 # LRU percent dirty begin cleaning limit LRU_MIN_DIRTY 0 # LRU percent dirty end cleaning limit LTXHWM 45 # Long transaction high water markpercentage LTXEHWM 50 # 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 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 # CDR Variables C

"Anderson, Andy" wrote: > > We are experiencing performance issues since upgrading to AIX 4.3.3 from > 4.3.2. The Informix database configuration has not changed and all the > latest patches/fixes have been applied to the OS. We are running on a > AIX4.3.3 / Informix7.31.UC3X1 / BAAN4C3(level 1 driver) environment. We have > also noted that when the onbar backups run (particularly level 0) we see > checkpoints as high as 30 minutes. > > Any help / suggestions would be greatly appreciated. I can supply any other > necessary info if requested. > > Thanks, Andy > > We have an S7A 12 cpu / 6 gig / ssa striped and OS mirrored. We also run > Baan on this server for batch jobs. All the users are tcp GUI Baan clients > (rexec). A typical "sar 5 5" shows: > > 11:37:22 %usr %sys %wio %idle > 11:37:27 8 21 0 71 > 11:37:32 9 21 0 70 > 11:37:37 9 21 0 69 > 11:37:42 7 20 0 73 > 11:37:47 9 21 0 70> > Average 9 21 0 71 > =========================================================================== > Provided below are the onconfig, onstat -g mgm, onstat -g iov, sqlhosts > =========================================================================== > ONCONFIG > =========================================================================== > #************************************************************************** > # > # INFORMIX SOFTWARE, INC. > # > # Title: onconfig.baansv01 for 7.31.UC3X1 > # Description: Informix Dynamic Server Configuration Parameters > # > #************************************************************************** > > # Root Dbspace Configuration > > ROOTNAME rootdbs # Root dbspace name> ROOTPATH /usr/Informix/links/Infmx400Root # containing root dbspace > ROOTOFFSET 64 # Offset of root dbspace into device > (Kbytes) > ROOTSIZE 350000 # Size of root dbspace (Kbytes)> > # Disk Mirroring Configuration Parameters > > MIRROR 1 # Mirroring flag (Yes = 1, No = 0) > MIRRORPATH # device containing mirrored root > MIRROROFFSET 0 # Offset into mirrored device> > # Physical Log Configuration > > PHYSDBS physdbs # Location (dbspace) of physical log > PHYSFILE 699788 # Physical log file size (Kbytes)> > # Logical Log Configuration > > LOGFILES 81 # Number of logical log files > LOGSIZE 5000 # Logical log size (Kbytes)> > # Diagnostics > > MSGPATH /usr/Informix/online.log # System message log file path > CONSOLE /usr/Informix/console.log # console message path > ALARMPROGRAM /usr/Informix/etc/log_full.sh # Alarm program path > SYSALARMPROGRAM /usr/Informix/etc/evidence.sh # System Alarm program path > # TBLSPACE_STATS 1 > > # System Archive Tape Device > > TAPEDEV /dev/rmt0 # Tape device path> #TAPEDEV /dev/null # Tape device path > TAPEBLK 512 # Tape block size (Kbytes) > TAPESIZE 10000000 # Maximum amount of data to put on tape > (Kbytes)> > # Log Archive Tape Device > > LTAPEDEV /dev/rmt0 # Log tape device path> #LTAPEDEV /dev/null # Log tape device path > LTAPEBLK 512 # Log tape block size (Kbytes) > LTAPESIZE 8000000 # Max amount of data to put on log tape > (Kbytes)> > # Optical > > STAGEBLOB # Informix Dynamic Server/Optical staging > area > > # System Configuration > > SERVERNUM 1 # Unique id corresponding to a Dynamic> Server instance > DBSERVERNAME baan01b # Name of default database server> DBSERVERALIASES baansv01,baansv01_str,baansv01_shm > # List of alternate dbservernames > NETTYPE ipcstr,1,40,NET # Configure poll thread(s) for nettype > NETTYPE ipcshm,1,40,CPU # Configure poll thread(s) for nettype For best load balancing and responsiveness have a SHM poll thread in every CPU VP: NETTYPE ipcshm,10,40,CPU > NETTYPE soctcp,2,300,NET # Configure poll thread(s) for nettype > NETTYPE sqlmux,1,20,NET # 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) RESIDENT does not work in AIX, right? [SNIP] Not much to work with. Most parameters look OK. Post onstat -p, onstat -g iof, onstat -g ioq, onstat -P|tail, onstat -F, onstat -R, onstat -l|head -15 to give us more to work with, include at least on onstat header line and let us know the last time you ran onstat -z if after startup. Art S. Kagel

Do the checkpoints climb only during onbar? We had a problem with a version of AIX (early 4) where all checkpoints climbed as soon as we upgraded. When from seconds to minutes. Needed a patch from IBM to fix. Turns out the type of I/O it did during the writing of the Phys log file was incorrect.