Re: Comment on my config

Bjorn De Waele wrote: > > Hello, > > here is our newbie again :) > I've been reading a lot lately, I searched the internet and browsed the > newsgroups to gather all my info. > I would like to thank especially Art Kagel, Neil Truby, Jonathan Leffler and > in fact so many other people here ! Cause you guys helped me through it ! > You're all a lot more clear then IBM docs ;) > > I'm playing around with our new servers. We made an import off the existing > data. > Our server is a HP proliant with 4 processors, 3 physical disks (one with > data for the moment, thinking of placing the most accessed data on the > second physical disk), 2 gig of Ram. Running on Win2003 with version 9.4 > We have in our current environment 8 chunks which I want to reduce to 1 > chunk if we go live (after last import). If we go live, I'll import, drop > stats, run update stat medium and run update stats high for the indexes. > I can't give you yet much statistics from onstat cause we're testing it > right now. > > This is my onconfig.... I really hope you can help me out if I overlooked > some things ! Pretty much is clearing up in my head but there's still so > much fuzzy for me:) > > Thanks a lot, Bjorn > > #************************************************************************** > # > # INFORMIX SOFTWARE, INC. > # > # Title: onconfig.std > # Description: Informix Dynamic Server Configuration Parameters > # > #************************************************************************** > > # Root Dbspace Configuration > > ROOTNAME rootdbs # Root dbspace name > ROOTPATH E:\\data\\rootdbs.000 # Path for device containing root dbspace > ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) > ROOTSIZE 100000 # 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 plogdbs # Location (dbspace) of physical log > PHYSFILE 40000 # Physical log file size (Kbytes)> > # Logical Log Configuration > > LOGFILES 178 # Number of logical log files > LOGSIZE 2000 # Logical log size (Kbytes)> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) > > # Diagnostics > > MSGPATH C:\\Informix\\ol_ouden.log # System message log file path > CONSOLE C:\\Informix\\conol_ouden.log # System console message path > > # To automatically backup logical logs, edit alarmprogram.bat and set > # BACKUPLOGS=Y > ALARMPROGRAM C:\\Informix\\etc\\alarmprogram.bat # Alarm program path > TBLSPACE_STATS 1 # Maintain tblspace statistics> > # System Diagnostic Script. > # SYSALARMPROGRAM - Full path of the system diagnostic script (e.g. > # c:\\informix\\etc\\evidence.bat.) Set this parameter > # if you want a different Diagnostic Script than > # {INFORMIXDIR}\\etc\\evidence.bat, which is default. > > # System Archive Tape Device > > #TAPEDEV \\\\.\\TAPE0 # Tape device path > TAPEDEV D:\\BACKUP > TAPEBLK 16 # Tape block size (Kbytes) > TAPESIZE 200000000 # Maximum amount of data to put on tape (Kbytes)> > # Log Archive Tape Device > > LTAPEDEV NUL # 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 Dynamic Server/Optical staging > area > OPTICAL_LIB_PATH # Location of Optical Subsystem driver DLL > > # System Configuration > > SERVERNUM 0 # Unique id corresponding to a server instance > DBSERVERNAME ol_ouden # Name of default Dynamic Server > DBSERVERALIASES # List of alternate dbservernames > NETTYPE onsoctcp,1,,NET # Override sqlhosts nettype parameters > 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 for> multi-processor > NUMCPUVPS 6 # Number of user (cpu) vps > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to> one > > NOAGE 0 # Process aging > AFF_SPROC 0 # Affinity start processor > AFF_NPROCS 0 # Affinity number of processors> > # Shared Memory Parameters > > LOCKS 200000 # Maximum number of locks > BUFFERS 200000 # Maximum number of shared buffers > NUMAIOVPS 12 # Number of IO vps #Initieel leeg > PHYSBUFF 64 # Physical log buffer size (Kbytes) #Initieel 32 > LOGBUFF 64 # Logical log buffer size (Kbytes) #Initieel 32 > CLEANERS 8 #1 # Number of buffer cleaner processes ->> normaal 1 per chunk > SHMBASE 0xC000000L # Shared memory base address > SHMVIRTSIZE 300000 # 54975 #8192 # initial virtual shared memory> segment size > SHMADD 20000 # Size of new shared memory segments > (Kbytes) > SHMTOTAL 1500000 # Total shared memory (Kbytes). > 0=>unlimited # initieel 0 > CKPTINTVL 300 # Check point interval (in sec) > LRUS 8 # Number of LRU queues > LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit > LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit > TXTIMEOUT 0x66c # Transaction timeout (in sec) > STACKSIZE 64 # Stack size (Kbytes)> > # Dynamic Logging > # DYNAMIC_LOGS: > # 2 : server automatically add a new logical log when necessary. (ON) > # 1 : notify DBA to add new logical logs when necessary. (ON) > # 0 : cannot add logical log on the fly. (OFF) > # > # When dynamic logging is on, we can have higher values for LTXHWM/LTXEHWM, > # because the server can add new logical logs during long transaction > rollback. > # However, to limit the number of new logical logs being added, > LTXHWM/LTXEHWM > # can be set to smaller values. > # > # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller values > # to avoid long transaction rollback hanging the server due to lack of > logical > # log space, i.e. 50/60 or lower. > > DYNAMIC_LOGS 2 > LTXHWM 40 > LTXEHWM 50> [... partly snipped ... ] I must keep this very unspecific, as I do not have any experience running IDS on Microsoft operating systems. You use approx 1 GB of your storage for the database. This seems reasonable, but if this machine is a database server and has no other duties, then maybe you will want to use more memory, that is increase BUFFERS by 25%. Compared to your BUFFERS, SHMVIRTSIZE seems high. What do you see in onstat -g seg? Do you have many incore sorts or do you see big parts unused/free. If the latter, then lower SHMVIRTSIZE, until you start to have more than 1 V-segment. This is a way to find an optimal value (brute force, but it works). Goal is to have SHMVIRTSIZE as small as possible and to avoid to have more than 1 V-segment at the same time. LRU of 8 seems to be too low. 200.000 BUFFERS in only 8 queues that is 250

Hi Richard, thanks a lot for your good information ! I know what you mean about listening too a Windows user of Informix. But this doesn't worry me that much cause I don't need to finetune this machine that much. I just want to use the 'general' tuning of Informix (independent of the OS) Thank you Bjorn "Richard Kofler" <richard.kofler@chello.at> wrote in message news:40F634CB.9BB6C234@chello.at... > Bjorn De Waele wrote: > > > > Hello, > > > > here is our newbie again :) > > I've been reading a lot lately, I searched the internet and browsed the > > newsgroups to gather all my info. > > I would like to thank especially Art Kagel, Neil Truby, Jonathan Leffler and > > in fact so many other people here ! Cause you guys helped me through it ! > > You're all a lot more clear then IBM docs ;) > > > > I'm playing around with our new servers. We made an import off the existing > > data. > > Our server is a HP proliant with 4 processors, 3 physical disks (one with > > data for the moment, thinking of placing the most accessed data on the > > second physical disk), 2 gig of Ram. Running on Win2003 with version 9.4 > > We have in our current environment 8 chunks which I want to reduce to 1 > > chunk if we go live (after last import). If we go live, I'll import, drop > > stats, run update stat medium and run update stats high for the indexes. > > I can't give you yet much statistics from onstat cause we're testing it > > right now. > > > > This is my onconfig.... I really hope you can help me out if I overlooked > > some things ! Pretty much is clearing up in my head but there's still so > > much fuzzy for me:) > > > > Thanks a lot, Bjorn > > > > #************************************************************************** > > # > > # INFORMIX SOFTWARE, INC. > > # > > # Title: onconfig.std > > # Description: Informix Dynamic Server Configuration Parameters > > # > > #************************************************************************** > > > > # Root Dbspace Configuration > > > > ROOTNAME rootdbs # Root dbspace name > > ROOTPATH E:\\data\\rootdbs.000 # Path for device containing root dbspace > > ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) > > ROOTSIZE 100000 # 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 plogdbs # Location (dbspace) of physical log > > PHYSFILE 40000 # Physical log file size (Kbytes)> > > > # Logical Log Configuration > > > > LOGFILES 178 # Number of logical log files > > LOGSIZE 2000 # Logical log size (Kbytes)> > LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) > > > > # Diagnostics > > > > MSGPATH C:\\Informix\\ol_ouden.log # System message log file path > > CONSOLE C:\\Informix\\conol_ouden.log # System console message path > > > > # To automatically backup logical logs, edit alarmprogram.bat and set > > # BACKUPLOGS=Y > > ALARMPROGRAM C:\\Informix\\etc\\alarmprogram.bat # Alarm program path > > TBLSPACE_STATS 1 # Maintain tblspace statistics> > > > # System Diagnostic Script. > > # SYSALARMPROGRAM - Full path of the system diagnostic script (e.g. > > # c:\\informix\\etc\\evidence.bat.) Set this parameter > > # if you want a different Diagnostic Script than > > # {INFORMIXDIR}\\etc\\evidence.bat, which is default. > > > > # System Archive Tape Device > > > > #TAPEDEV \\\\.\\TAPE0 # Tape device path > > TAPEDEV D:\\BACKUP > > TAPEBLK 16 # Tape block size (Kbytes) > > TAPESIZE 200000000 # Maximum amount of data to put on tape (Kbytes)> > > > # Log Archive Tape Device > > > > LTAPEDEV NUL # 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 Dynamic Server/Optical staging > > area > > OPTICAL_LIB_PATH # Location of Optical Subsystem driver DLL > > > > # System Configuration > > > > SERVERNUM 0 # Unique id corresponding to a server instance > > DBSERVERNAME ol_ouden # Name of default Dynamic Server > > DBSERVERALIASES # List of alternate dbservernames > > NETTYPE onsoctcp,1,,NET # Override sqlhosts nettype parameters > > 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 for> > multi-processor > > NUMCPUVPS 6 # Number of user (cpu) vps > > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vpsto > > one > > > > NOAGE 0 # Process aging > > AFF_SPROC 0 # Affinity start processor > > AFF_NPROCS 0 # Affinity number of processors> > > > # Shared Memory Parameters > > > > LOCKS 200000 # Maximum number of locks > > BUFFERS 200000 # Maximum number of shared buffers > > NUMAIOVPS 12 # Number of IO vps #Initieel leeg > > PHYSBUFF 64 # Physical log buffer size (Kbytes) #Initieel 32 > > LOGBUFF 64 # Logical log buffer size (Kbytes) #Initieel 32 > > CLEANERS 8 #1 # Number of buffer cleaner processes ->> > normaal 1 per chunk > > SHMBASE 0xC000000L # Shared memory base address > > SHMVIRTSIZE 300000 # 54975 #8192 # initial virtual sharedmemory > > segment size > > SHMADD 20000 # Size of new shared memory segments > > (Kbytes) > > SHMTOTAL 1500000 # Total shared memory (Kbytes). > > 0=>unlimited # initieel 0 > > CKPTINTVL 300 # Check point interval (in sec) > > LRUS 8 # Number of LRU queues > > LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit > > LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit > > TXTIMEOUT 0x66c # Transaction timeout (in sec) > > STACKSIZE 64 # Stack size (Kbytes)> > > > # Dynamic Logging > > # DYNAMIC_LOGS: > > # 2 : server automatically add a new logical log when necessary. (ON) > > # 1 : notify DBA to add new logical logs when necessary. (ON) > > # 0 : cannot add logical log on the fly. (OFF) > > # > > # When dynamic logging is on, we can have higher values for LTXHWM/LTXEHWM, > > # because the server can add new logical logs during long transaction > > rollback. > > # However, to limit the number of new logical logs being added, > > LTXHWM/LTXEHWM > > # can be set to smaller values. > > # > > # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller values > > # to avoid long transaction rollback hanging the server due to lack of > > logical > > # log space, i.e. 50/60 or lower. > > > > DYNAMIC_LOGS 2 > > LTXHWM 40 > > LTXEHWM 50> > > > [... partly snipped ... ] > > I must kee