Informix Perf Question
Posted in 1994
I have setup an informix database on a Sparc10. 5.00.UC3. The
configuration is generally the same as other servers I have but it runs
different applications. I have noticed that this server generally has
0% - 30% cache reads and 80% - 95% cache writes. On the other servers
the cache read and write range from the high 80% to 90+%. Is it possible
that the applicationbs software is negatively impacting the cache %??
The database is spread across 5 disks over two controllers. It is
mirrored and has buffered logging. The configuration is listed below. Any
ideas would be greatly appreciated.
Wayne
#**************************************************************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: tbconfig.std
# Sccsid: @(#)tbconfig.std 8.8 9/26/91 14:16:33
# Description: INFORMIX-OnLine Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/online_root # Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device
ROOTSIZE 394800 # Size of root dbspace (Kbytes)
# Disk Mirroring Configuration
MIRROR 1 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH /dev/online_root_m
MIRROROFFSET 0 # Offset into mirror device (Kbytes)
# Physical Log Configuration
PHYSDBS rootdbs # Name of dbspace that contains
PHYSFILE 100000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 26 # Number of logical log files
LOGSIZE 6000 # Size of each logical log file (Kbytes)
# Message Files
MSGPATH /usr/local/informix/online.log # OnLine message
CONSOLE /dev/console # System console message pathname
# Archive Tape Device
TAPEDEV /dev/rst24 # Archive tape device pathname
TAPEBLK 126 # Archive tape block size (Kbytes)
TAPESIZE 5000000 # Max amount of data to put on
# Logical Log Backup Tape Device
LTAPEDEV /dev/rst24 # Logical log tape device pathname
LTAPEBLK 126 # Logical log tape block size
LTAPESIZE 5000000 # Max amount of data to put
# Identification Parameters
SERVERNUM 0 # Unique id associated with
DBSERVERNAME db1 # Unique name of this OnLine
# Shared Memory Parameters
RESIDENT 0 # Forced residency flagUSERS 250 # Maximum number of concurrent user
TRANSACTIONS 500 # Maximum number of concurrent
LOCKS 200000 # Maximum number of locks
BUFFERS 12000 # Maximum number of shared memory buffersTBLSPACES 5000 # Maximum number of active tblspaces
CHUNKS 16 # Maximum number of chunks
DBSPACES 16 # Maximum number of dbspaces and blobspaces
PHYSBUFF 64 # Size of physical log buffers (Kbytes)
LOGBUFF 64 # Size of logical log buffers (Kbytes)LOGSMAX 60 # Maximum number of logical log files
CLEANERS 5 # Number of page-cleaner processes
SHMBASE 0x10000000 # Shared memory base address
CKPTINTVL 1800 # Checkpoint interval (in seconds)
LRUS 8 # Number of LRU queues
LRU_MAX_DIRTY 10 # LRU modified begin-cleaning limit
LRU_MIN_DIRTY 5 # LRU modified end-cleaning limit
LTXHWM 70 # Long TX high-water mark (percent)
LTXEHWM 80 # Long TX exclusive high-water mark
# Machine- and Product-Specific Parameters
DYNSHMSZ 0 # Dynamic shared memory size (Kbytes)
GTRID_CMP_SZ 32 # Number of bytes to use in GTRID comparision
DEADLOCK_TIMEOUT 60 # Max time to wait for lock in
TXTIMEOUT 300 # Transaction timeout for I-STARSPINCNT 0 # No. of times process tries for latch
STAGEBLOB # Reserved for INFORMIX-OnLine/Optical
# System Page Size
BUFFSIZE 2048 # Page size (do not change!)