Re: Baan on Informix 7.23 UC6

From: "Tony Cullen" <acullen@global.co.za> > >Please ignore my last posting as I sent it as an attachment. I then noticed >that noone >else does this so here it comes without the attachment. > >Hope someone can help here. We migrated from running BAAN IVc0 on tbase to >running it on >Informix version 7.23 UC6 over the weekend. Our porting set is 6.1c.04.01 >and we are >running on an AIX model F40 2 processor 166Mhz under AIX version 4.3. Since >the migration >our througput has gone out by a factor of 3-4 i.e jobs that took 10mins now >run for 30-40 >mins.Can you check the stats below and if you need any other stats let me >know and I can >supply them. These were taken using the level 1 driver supplied by Baan but >I believe that >there is a level 2 driver for Informix on Baan which could improve matters. Allegedly. I've never actually seen it in use. But because of the way Baan access data using the level one drivers, nothing can beat the Baan "database engine" for performance. You would be able to do a lot more at the Informix level to tune performance if you were using the level 2 drivers. If they exist. :-) >Has anyone >had any experience with it. For the meantime I would appreciate it if you >could give me >some pointers regarding the config to see if we can fix the existing setup. I hate to say this, but this looks like a pretty well-tuned instance. You would probably only be able to improve things with faster CPUs and more spindles. But some comments are embedded further along. >THE STATS WHERE ZEROISED AT 10am and these readings were taken at 8:30 pm >so they relect a days work. > > >#************************************************************************** ># ># INFORMIX SOFTWARE, INC. ># ># Title: onconfig.std ># Description: INFORMIX-OnLine Configuration Parameters ># >#************************************************************************** > ># Root Dbspace Configuration > >ROOTNAME rootdbs # Root dbspace name >ROOTPATH /dev/Iinfrootdbs # Path for device containing root dbspace >ROOTOFFSET 0 # Offset of root dbspace into device >(Kbytes) >ROOTSIZE 240000 # 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) Are you using RAID? If so, I hope it's not RAID 5. If not, what are you doing for resilience? ># Physical Log Configuration > >PHYSDBS phydbs # Location (dbspace) of physical log >PHYSFILE 270000 # Physical log file size (Kbytes)> ># Logical Log Configuration > >LOGFILES 19 # Number of logical log files >LOGSIZE 10000 # Logical log size (Kbytes)> ># Diagnostics > >MSGPATH /usr/informix/online.log # System message log file path >CONSOLE /dev/console # System console message path >ALARMPROGRAM /usr/informix/etc/log_full.sh # Alarm program path> ># System Archive Tape Device > >TAPEDEV /dev/rmt0 # Tape device path >TAPEBLK 1024 # Tape block size (Kbytes) >TAPESIZE 7900000 # Maximum amount of data to put on tape >(Kbytes)> ># Log Archive Tape Device > >LTAPEDEV /dev/rmt0 # Log tape device path >LTAPEBLK 1024 # Log tape block size (Kbytes) >LTAPESIZE 7900000 # Max amount of data to put on log tape >(Kbytes)> ># Optical > >STAGEBLOB ,1 # INFORMIX-OnLine/Optical staging area > ># System Configuration > >SERVERNUM 0 # Unique id corresponding to a OnLine>instance >DBSERVERNAME baan_str # Name of default database server >DBSERVERALIASES baan_shm # List of alternate dbservernames >NETTYPE ipcstr,1,100,CPU # Configure poll thread(s) for nettype >NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) for nettype >NETTYPE sqlmux,1,100,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) IBM, right? :^) >MULTIPROCESSOR 1 # 0 for single-processor, 1 for>multi-processor >NUMCPUVPS 2 # Number of user (cpu) vps >SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to>one Have you tried MULTIPROCESSOR 0 # 0 for single-processor, 1 for NUMCPUVPS 1 # Number of user (cpu) vps SINGLE_CPU_VP 1 # If non-zero, limit number of cpu? >NOAGE 1 # Process aging >AFF_SPROC 0 # Affinity start processor >AFF_NPROCS 0 # Affinity number of processors> ># Shared Memory Parameters > >LOCKS 580000 # Maximum number of locks >BUFFERS 40000 # 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) Judging by the output from onstat -l, you can up PHYSBUFF and LOGBUFF. Try 64 each. >LOGSMAX 100 # Maximum number of logical log files >CLEANERS 7 # Number of buffer cleaner processes >SHMBASE 0x30000000 # Shared memory base address >SHMVIRTSIZE 160000 # initial virtual shared memory segment>size >SHMADD 50000 # Size of new shared memory segments >(Kbytes) >SHMTOTAL 0 # Total shared memory (Kbytes). >0=>unlimited >CKPTINTVL 300 # Check point interval (in sec) >LRUS 7 # Number of LRU queues >LRU_MAX_DIRTY 12 # LRU percent dirty begin cleaning limit >LRU_MIN_DIRTY 8 # 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 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 ># DRA