Re: Online 7.12 Tunning

In article <19970917025700.WAA00456@ladder02.news.aol.com>, SaTriGuy <satriguy@aol.com> writes >I'm including some remarks at the end as well as embedding some things >within the copy. > >M.Pruet > >> >>Hello, >> >>I've just upgraded from Online 5 to Online 7.12, on a RISC6000 with >>128MB RAM, and I'm having some performance problems. > >Is there a reason that you chose to go to 7.12 instead of 7.14? There are >several performance problems that have been corrected since the 7.12 days. >Also, some of the key tools that can be used in diagnosis of performance >issues do not work correctly in 7.12. > > >>The database is about 400MB and I have 32 users running an MRP application. >>Can someone give me some hints on this? >> People are currently guessing - first we need some answers:- Hardware -------- How many CPUS do you have on the machine? How many physical disks and what size? Do you use a Logical Volume Manager and if so how are the volumes laid out? UNIX ---- what does the command sar -r 1 3 show? what are the top ten processes clocking up CPU time in ps -aux (or ps -ef whichever works)? Informix -------- What does onstat -u show? What does onstat -g ath show? What does onstat -p show What does onstat -g seg show? What does onstat -d show? >>Thanks in advance. >> >>This is my onconfig file: >> >> >>#************************************************************************** >># >># INFORMIX SOFTWARE, INC. >># >># Title: onconfig.std >># Description: INFORMIX-OnLine Configuration Parameters >># >>#************************************************************************** >> >># Root Dbspace Configuration >> >>ROOTNAME rlv02 # Root dbspace name >>ROOTPATH /dev/rlv02 # Path for device containing root dbspace >>ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) >>ROOTSIZE 122880 # 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 rlv02 # Location (dbspace) of physical log >>PHYSFILE 10240 # Physical log file size (Kbytes)>> >># Logical Log Configuration >> >>LOGFILES 12 # Number of logical log files >>LOGSIZE 5120 # Logical log size (Kbytes)>> >># Diagnostics >> >>MSGPATH /online7/online.log # System message log file path >>CONSOLE /dev/console # System console message path >>ALARMPROGRAM # Alarm program path>> >># System Archive Tape Device >> >>TAPEDEV /dev/rmt0 # Tape device path >>TAPEBLK 512 # Tape block size (Kbytes) >>TAPESIZE 1227776 # 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-OnLine/Optical staging area >> >># System Configuration >> >>SERVERNUM 0 # Unique id corresponding to a OnLine>>instance >>DBSERVERNAME dpx20 # Name of default database server >>DBSERVERALIASES dpx20_ip # List of alternate dbservernames >>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 for>>multi-processor >>NUMCPUVPS 1 # Number of user (cpu) vps> >Is there really only a single physical cpu on the system? > >>SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps to one >> >>NOAGE 1 # Process aging> >My guess is that you are running your client applications on the same >system via shared memory. If that is the case, you might have to turn off >NOAGE and use nice to keep the priority up. > >>AFF_SPROC 0 # Affinity start processor >>AFF_NPROCS 0 # Affinity number of processors>> >># Shared Memory Parameters >> >>LOCKS 60000 # Maximum number of locks >>BUFFERS 7200 # Maximum number of shared buffers >>NUMAIOVPS 1 # Number of IO vps> >If you are using KAIO, then you will only have one kaio thread on the >single cpuvp. If you are not using KAIO, then you need more IOVPS > >>PHYSBUFF 64 # Physical log buffer size (Kbytes) >>LOGBUFF 64 # Logical log buffer size (Kbytes)>>LOGSMAX 12 # Maximum number of logical log files >>CLEANERS 3 # Number of buffer cleaner processes >>SHMBASE 0x30000000 # Shared memory base address >>SHMVIRTSIZE 16000 # 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 10 # LRU percent dirty begin cleaning limit >>LRU_MIN_DIRTY 20 # LRU percent dirty end cleaning>limit > >You might want to decrease LRU MAX/MIN even more > >>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 >># 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