Re: Performance Issues

In article <8isudo$lq2$1@news.xmission.com>, Isidre PONS ROCA <ipons@dtgna.altanet.org> writes > >En yener@my-deja.com va escriure el dia 21 Jun 2000, a les 19:01: > >> Hi, >> >> We are currently running informix on E5000 system which 4 CPUs and 2 MB >> of RAM. We have got some performance problems on this system. >> > 2Mb or 2Gb? > >> The performance of the application running on this system is not >> comparable what we had expected. The system is a batch processing >> system. >> >> We analys the system and unable to find any suitable solution to >> improve performance. >> >> The listing below shows the output of onstat -p. >> ================================================ >> >> dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached >> 4043750739 59853281 604861800 0.00 122732622 70823866 1106184833 >> 88.90 >> >> isamtot open start read write rewrite delete commit >> rollbk >> 1018217434 2365010653 400986740 1380105727 152884987 127463044 8803283 >> 39620880 >> 366903 >> >> gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs >> 0 0 0 0 0 0 0 >> >> ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes >> 0 0 0 2000759.78 364288.72 8828 18200 >> >> bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans >> 179603434 0 3227542476 0 0 18465 9537417 >> 11416813 >> >> ixda-RA idx-RA da-RA RA-pgsused lchwaits >> 1492613204 3357525 1959151075 3444017014 21784573 >> >> and the following listing shows our onconfig file >> ================================================== >> >> #*********************************************************************** >> *** >> # >> # INFORMIX SOFTWARE, INC. >> # >> # Title: onconfig.std >> # Description: Informix Dynamic Server Configuration Parameters >> # >> #*********************************************************************** >> *** >> >> # Root Dbspace Configuration >> >> ROOTNAME rootdbs # Root dbspace name >> ROOTPATH /export/home/ifmxdata/s01_01>> # Path for device containing root >> dbspace >> ROOTOFFSET 0 # Offset of root dbspace into device >> (Kbytes) >> ROOTSIZE 2000000 # 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 1000000 # Physical log file size (Kbytes)>> Move this into a separate dbspace on another disk. >> # Logical Log Configuration >> >> LOGFILES 600 # Number of logical log files>Increase the number of log files > LOGFILES 2400 >> LOGSIZE 20000 # Logical log size (Kbytes)>> Change to LOGSIZE 1000 and adjust LOGFILES as required. > >Decrease de log size. > LOGSIZE 5000> >> # Diagnostics >> >> MSGPATH /export/home/informix/online.log # System message log >> file path >> CONSOLE /dev/console # System console message path >> ALARMPROGRAM /export/home/informix/etc/log_full.sh # Alarm program>> path >> SYSALARMPROGRAM /export/home/informix/etc/evidence.sh >> # System Alarm program path >> TBLSPACE_STATS 1>> >> # System Archive Tape Device >> TAPEDEV /export/home/ifmxdata/tape0 # Tape device path >> TAPEBLK 16 # Tape block size (Kbytes) >> TAPESIZE 90000000 # Maximum amount of data to put on >> tape (Kbytes) Increase TAPEBLK to 1024 to reduce the time taken for archive. >> >> # Log Archive Tape Device >> >> LTAPEDEV /export/home/ifmxdata/tape1 # Log tape device path >> LTAPEBLK 16 # Log tape block size (Kbytes) >> LTAPESIZE 40000000 # Max amount of data to put on log >> tape (Kbytes)>> Increase this to 1024 as well. > >> # Optical >> >> STAGEBLOB # Informix Dynamic Server/Optical >> staging area >> >> # System Configuration >> >> SERVERNUM 0 # Unique id corresponding to a Dynamic>> Server instance >> DBSERVERNAME prime # Name of default database server >> DBSERVERALIASES kocprime # 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)>> Set RESIDENT = 1 > >> MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi->> processor >> NUMCPUVPS 4 # Number of user (cpu) vps >> SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps>> to one >> > > >> NOAGE 1 # Process aging >> AFF_SPROC 0 # Affinity start processor >> AFF_NPROCS 0 # Affinity number of processors >Try : > MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi->processor > NUMCPUVPS 3 # Number of user (cpu) vps > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one > > NOAGE 1 # Process aging > AFF_SPROC 1 # Affinity start processor > AFF_NPROCS 3 # Affinity number of processors> Or even NUMCPUVPS 4, AFF_NPROCS = 4>> >> # Shared Memory Parameters >> >> LOCKS 5000000 # Maximum number of locks >> BUFFERS 400000 # Maximum number of shared buffers >> NUMAIOVPS 2 # Number of IO vps >> PHYSBUFF 512 # Physical log buffer size (Kbytes) >> LOGBUFF 512 # Logical log buffer size (Kbytes)>> LOGSMAX 600 # Maximum number of logical log files >> CLEANERS 32 # Number of buffer cleaner processes Increase to 127 >> SHMBASE 0xa000000 # Shared memory base address >> SHMVIRTSIZE 128000 # initial virtual shared memory segment>> size >> SHMADD 32000 # Size of new shared memory segments >> (Kbytes) >> SHMTOTAL 0 # Total shared memory (Kbytes). >> 0=>unlimited >> CKPTINTVL 300 # Check point interval (in sec) >> LRUS 127 # Number of LRU queues >> LRU_MAX_DIRTY 10 # LRU percent dirty begin cleaning limit >> LRU_MIN_DIRTY 5 # LRU percent dirty end cleaning limit >> LTXHWM 50 # Long transaction high water mark>> percentage >> LTXEHWM 60