Help with Informix !!! Really Important!!!
Posted in 2005
Topics: Installation, Setup & Upgrades, Storage & Space Management, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration
Hi all, I have an Informix Dinamic Server 9.24, installed in a Windows
Server 2003 Standard Edition with a PIII 930MHZ and 512MB RAM
The server have to Hd, one with 2.25Gb and another one with 8.
I also have an apllication that runs against Informix Database. When we
have in the database only a few records, the system is really fast, but
when it started to store more than about 100.000 records, it gets
really really slow.
We have tried to solve the problem by changing some configuration
parameters, and also we created a new DBSpace with 1.5GB, but it didn't
becomes better...
The app make some heavy operations against the DDBB, but it is slow
also when the operation just requires few records.
I post the ONCONFIG file, please, if you see something extrange, or you
can just help me in any way, I`ll been thankful
#**************************************************************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.std
# Description: Informix Dynamic Server Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace name
ROOTPATH C:\\IFMXDATA\\nomina\\rootdbs_dat.000 # Path for device containing root
dbspace
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 51200 # Size of root dbspace (Kbytes)
# Disk Mirroring Configuration Parameters
MIRROR 1 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH D:\\IFMXDATA\\nomina\\rootdbs_mirr.000
# Path for device containing mirrored
root
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)
# Physical Log Configuration
PHYSDBS rootdbs # Location (dbspace) of physical log
PHYSFILE 2000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 8 # Number of logical log files
LOGSIZE 2000 # Logical log size (Kbytes)LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL,
CONT)
# Diagnostics
MSGPATH C:\\PROGRA~1\\Informix\\nomina.log # System message log
file path
CONSOLE C:\\PROGRA~1\\Informix\\connomina.log # System console
message path
# To automatically backup logical logs, edit alarmprogram.bat and set
# BACKUPLOGS=Y
ALARMPROGRAM C:\\PROGRA~1\\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 NUL # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 10240 # 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 1 # Unique id corresponding to a serverinstance
DBSERVERNAME nomina # Name of default Dynamic Server
DBSERVERALIASES # List of alternate dbservernames
NETTYPE soctcp,1,,NET # Override sqlhosts nettype parameters
DEADLOCK_TIMEOUT 10 # Max time to wait of lock indistributed env.
RESIDENT 1 # 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 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
LOCKS 2000 # Maximum number of locks
BUFFERS 200000 # Maximum number of shared buffers
NUMAIOVPS 1 # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)
CLEANERS 128 # Number of buffer cleaner processes
SHMBASE 0xc000000 # Shared memory base address
SHMVIRTSIZE 8192 # 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 128 # Number of LRU queues
LRU_MAX_DIRTY 60.000000 # LRU percent dirty begin cleaninglimit
LRU_MIN_DIRTY 50.000000 # LRU percent dirty end cleaning limit
TXTIMEOUT 0x12c # 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 70
LTXEHWM 80
# 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
DRINTERVAL 30 # DR max time between DR buffer flushes
(in sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND
Add more RAM. In my experience with the combination of IDS 9.40 and Windows 2003, 512 MB is just not enough. The Task Manager Performance tab showed memory usage pegged. We jumped straight to 2 GB and that solved a lot of problems. Next, I notice you have no temp dbspace listed. That can be a big problem. Other than that, I would urge you to read the Performance Guide at http://publibfp.boulder.ibm.com/epubs/pdf/ct1t9na.pdf This will not only give you good advice about how to resolve most performance issues, it will give advice on how to identify them. You are using a vanilla, default onconfig file. Unfortunately, there is no such thing as a vanilla, default application. Without knowing more about your application, no one will be able to give you the Really Important!!! help you need. Sincerely, Christopher Coleman President Kansas City Informix Users Group www.iiug.org/kciug Database Analyst Medication Management Mediware Information Systems, Inc.
What about the old faithful "UPDATE STATISTICS". I would suggest that the queries are working on out of date statistics. If "UPDATE STATISTICS" doesn't improve matters reading up on UPDATE STATISTICS in the documentation. I'd even suggest using the IDS 10 documentation set as this has a search facility that will enable you to get to the right sections of the manuals very quickly. regards Malcolm Christopher wrote: > Add more RAM. > > In my experience with the combination of IDS 9.40 and Windows 2003, 512 > MB is just not enough. The Task Manager Performance tab showed memory > usage pegged. We jumped straight to 2 GB and that solved a lot of > problems. > > Next, I notice you have no temp dbspace listed. That can be a big > problem. > > Other than that, I would urge you to read the Performance Guide at > http://publibfp.boulder.ibm.com/epubs/pdf/ct1t9na.pdf > > This will not only give you good advice about how to resolve most > performance issues, it will give advice on how to identify them. > > You are using a vanilla, default onconfig file. Unfortunately, there > is no such thing as a vanilla, default application. Without knowing > more about your application, no one will be able to give you the Really > Important!!! help you need. > > Sincerely, > > Christopher Coleman > > President > Kansas City Informix Users Group > www.iiug.org/kciug > > Database Analyst > Medication Management > Mediware Information Systems, Inc.
9.24?
9.14 maybe
7.24 maybe
9.24?you sure
can you run onstat -V and post the output?
mweall...@panacea.co.uk wrote:
> What about the old faithful "UPDATE STATISTICS". I would suggest
that
> the queries are working on out of date statistics. If "UPDATE
> STATISTICS" doesn't improve matters reading up on UPDATE STATISTICS
in
> the documentation.
> I'd even suggest using the IDS 10 documentation set as this has a
> search facility that will enable you to get to the right sections of
> the manuals very quickly.
>
> regards
>
> Malcolm
>
> Christopher wrote:
> > Add more RAM.
> >
> > In my experience with the combination of IDS 9.40 and Windows 2003,
> 512
> > MB is just not enough. The Task Manager Performance tab showed
> memory
> > usage pegged. We jumped straight to 2 GB and that solved a lot of
> > problems.
> >
> > Next, I notice you have no temp dbspace listed. That can be a big
> > problem.
> >
> > Other than that, I would urge you to read the Performance Guide at
> > http://publibfp.boulder.ibm.com/epubs/pdf/ct1t9na.pdf
> >
> > This will not only give you good advice about how to resolve most
> > performance issues, it will give advice on how to identify them.
> >
> > You are using a vanilla, default onconfig file. Unfortunately,
there
> > is no such thing as a vanilla, default application. Without
knowing
> > more about your application, no one will be able to give you the
> Really
> > Important!!! help you need.
> >
> > Sincerely,
> >
> > Christopher Coleman
> >
> > President
> > Kansas City Informix Users Group
> > www.iiug.org/kciug
> >
> > Database Analyst
> > Medication Management
> > Mediware Information Systems, Inc.
Related threads
- onbar -c -F in Windows Informix instance
- Anyone... SQLCODE=-668, ISAM error=-1
- Not using the 100% logical log page size alloacted to informix