RE: Informix UC7.41 - slow

I would query how you can define that it is running slow when it is a test system. I have observed that IDS doesn't really ever start to make the most of the resources until you have a reasonable number of users doing reasonable work loads. I have production systems that say they're running slow and I find out they have 4 users and the cpus are 98% idle. They don't benefit from shared memory as they rarely read pages twice within a few days. I see you say you're using cooked files. Performance and cooked files are not commonly seen together. You can spend a lot of time trying to tune a test system and it won't bear any relevance to the live system. But generally I would suggest reading the Performance Guide manual. Set up the system according to that. Then read the cdi archives for all the improvements to LRUMIN, LRUMAX. No of LRUS etc. There are no easy answers to performance, and as I said before you can't expect good performance from a test system. But if you want to employ a consultant then ..... Regards Malcolm -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On Behalf Of Geezer From The Freezer Sent: 17 January 2005 16:37 To: informix-list@iiug.org Subject: Re: Informix UC7.41 - slow "Art S. Kagel" wrote: > > Geezer From The Freezer wrote: > > > > TBP wrote: > > > >>Geezer From The Freezer wrote: > >> > >>>Hi, > >>> > >>>My Informix installation seems to be running quite slowly. It's > >>>running on a Sun Blade 1000 with 2 x 750Mhz processors and 2Gb RAM. > >>> > >>>Here is the onconfig file - anything obviously wrong or tuneable? > >> > >>Yes :D > >> > >>No such version as UC7.41, but presumably this is something like > >>7.31.UC7?? > > > > > > oops. 7.31.UC5 even, my mistake :D > > OK, you're on the right track now. Repost your ONCONFIG info (so we > don't have to hunt down the original post) along with ALL of the > following and someone will help: > > Time since startup or since onstat -z was run if later. Output from: > onstat -p onstat -d > onstat -P > onstat -D > onstat -m > onstat -F > onstat -g glo > onstat -g iov > onstat -g iof > onstat -g rea> > Art S. Kagel ok ran onstat -z to remove stuff - ran some simple export commands from the application running over informix. Here is more info - onconfig file # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace name ROOTPATH /usr/informix/data/data1 # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 200000 # Size of root dbspace (Kbytes) # Disk Mirroring Configuration Parameters MIRROR 0 # Mirroring flag (Yes = 1, No = 0) MIRRORPATH # Path for device containing mirroredroot MIRROROFFSET 0 # Offset into mirrored device (Kbytes) # Physical Log Configuration PHYSDBS rootdbs # Physical log file size (Kbytes) PHYSFILE 32768 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 45 # Number of logical log files LOGSIZE 2048 # Logical log size (Kbytes) # Diagnostics MSGPATH /usr/informix/online.log # System message log file path CONSOLE /usr/informix/console.log # System 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/null # Tape device path TAPEBLK 256 # Tape block size (Kbytes) TAPESIZE 128000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /dev/null # Log tape device path LTAPEBLK 256 # Log tape block size (Kbytes) LTAPESIZE 128000 # Max amount of data to put on log tape (Kbytes) # Optical STAGEBLOB # System Configuration SERVERNUM 0 # Unique id corresponding to a DynamicServer instance DBSERVERNAME mlgw333 # Name of default database server DBSERVERALIASES # List of alternate dbservernames DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed 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 0 # If non-zero, limit number of cpu vpsto one NOAGE 1 AFF_SPROC 0 # Affinity start processor AFF_NPROCS 0 # Affinity number of processors # Shared Memory Parameters LOCKS 550000 # Maximum number of locks BUFFERS 50000 # Maximum number of shared buffers NUMAIOVPS # Number of IO vps PHYSBUFF 1024 # Size of root dbspace (Kbytes) LOGBUFF 1024 # Logical log buffer size (Kbytes)LOGSMAX 200 # Maximum number of logical log files CLEANERS 16 # Number of buffer cleaner processes SHMBASE 0xa000000 # Shared memory base address SHMVIRTSIZE 16384 # initial virtual shared memory segmentsize 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 16 # Number of LRU queues LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit LTXHWM 50 # Long transaction high water markpercentage LTXEHWM 60 # Long transaction high water mark (exclusive) TXTIMEOUT 0x4b0 # 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 workerthreads # Data Replication Variables # DRAUTO: 0 manual, 1 retain type, 2 reverse type DRAUTO 0

malcolm weallans wrote: > > I would query how you can define that it is running slow when it is a > test system. I have observed that IDS doesn't really ever start to make > the most of the resources until you have a reasonable number of users > doing reasonable work loads. I have production systems that say they're > running slow and I find out they have 4 users and the cpus are 98% idle. > They don't benefit from shared memory as they rarely read pages twice > within a few days. > I see you say you're using cooked files. Performance and cooked files > are not commonly seen together. You can spend a lot of time trying to > tune a test system and it won't bear any relevance to the live system. > But generally I would suggest reading the Performance Guide manual. Set > up the system according to that. Then read the cdi archives for all the > improvements to LRUMIN, LRUMAX. No of LRUS etc. There are no easy > answers to performance, and as I said before you can't expect good > performance from a test system. > > But if you want to employ a consultant then ..... > Like I said, I have two test systems. One running on a Solaris Ultra 10 with 512Mb RAM and a 440Mhz processor. Restoring data on there is 3 times faster. On the Blade 1000 with 2 x 750Mhz processors and 2Gb RAM it takes 3 times longer. These systems are only used to restore data and then extract sections of data into XML Format.