Scope change.
Posted in 2004
Topics: High Availability & Replication, Performance & Tuning, Storage & Space Management, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration
I have been gathering information about this system. At the end
really strange things end up not being true. This is another time it
happens.
Though the people that were responsible of this before -and supposed
to be knowledgeable in Informix- told me the system I posted the other day
was not good, I have been doing some testing using LoadRunner and I found
what I was told do not seem to be right.
At the end, all the reporting functionality in the application goes
against another Informix instance. We could say the "online" functionality
goes against the Informix I posted the other day and that "reports" go
against the Informix instance that shows poor performance. Between these two
systems there is transactional replication, which I do not know very well in
Informix.
The onconfig for this system looks like:
#**************************************************************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.std
# Description: Informix Dynamic Server Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace name
ROOTPATH X:\\IFMXDATA\\ol_espmadinformix2\\rootdbs_dat.000
#Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 30720 # 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 physdbs # Location (dbspace) of physical log
PHYSFILE 80000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 10 # Number of logical log files
LOGSIZE 1500 # Logical log size (Kbytes)LOG_BACKUP_MODE CONT # Logical log backup mode (MANUAL, CONT)
# Diagnostics
MSGPATH X:\\IFMXDATA\\ol_replica.log # System message log file path
CONSOLE X:\\IFMXDATA\\conol_replica.log # System console message path
# To automatically backup logical logs, edit alarmprogram.bat and set
# BACKUPLOGS=Y
ALARMPROGRAM E:\\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
TAPEDEV L:\\copia # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 75000000 # Maximum amount of data to put on tape (Kbytes)
# Log Archive Tape Device
LTAPEDEV X:\\copilog # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 80000000 # 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 OnLine instance
DBSERVERNAME ol_replica # Name of default database server
DBSERVERALIASES # List of alternate dbservernames
NETTYPE soctcp,2,500,NET # Override sqlhosts nettype parameters
DEADLOCK_TIMEOUT 90 # Max time to wait of lock in distributed env.
#RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
RESIDENT 1 # Forced residency flag (Yes = 1, No = 0)
MULTIPROCESSOR 1 # 0 for single-processor, 1 formulti-processor
NUMCPUVPS 2 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps toone
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
LOCKS 500000 # Maximum number of locks#BUFFERS 200000 # Maximum number of shared buffers
BUFFERS 300000 # Maximum number of shared buffers
NUMAIOVPS 1 # Number of IO vps
PHYSBUFF 128 # Physical log buffer size (Kbytes)
#LOGBUFF 64 # Logical log buffer size (Kbytes)
LOGBUFF 16 # Logical log buffer size (Kbytes)
CLEANERS 8 # Number of buffer cleaner processes
SHMBASE 0xC000000L # Shared memory base address#SHMVIRTSIZE 128000 # initial virtual shared memory segment size
SHMVIRTSIZE 256000 # initial virtual shared memory segment size
SHMADD 32768 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)#LRUS 64 # Number of LRU queues
LRUS 256 # Number of LRU queues
LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit
TXTIMEOUT 300 # 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 0
LTXHWM 45
LTXEHWM 50
# 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 worker threads
ON_RECVRY_THREADS 1 # Default number of online worker threads
# Data Replication Variables
DRINTERVAL 30 # DR max time between DR buffer flushes (in sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND E:\\INFORMIX\\tmp # DR lost+found file path
# CDR Variables
CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
CDR_QUEUEMEM 4096 # Maximum memory for any CDR queue (Kbytes)
CDR_QHDR_DBSPACE # CDR queue dbspace (default same as catalog)
CDR_QDATA_SBSPACE # CDR queue smart blob space
CDR_QDATA_SBFLAGS 2 # L
Leopold, If most of your tasks are reporting only and you are using HDR as the log you posted shows, why not run the read only reporting tasks on the DR secondary and reduce the load on your primary server? On a point of information HDR, which you call transactional replication, is very different to the feature of the same name in MS SQL Server. To improve performance try setting OPTCOMPIND to 0. It may persuade the optmiser to use better query plans. Also if you aren't using your table space statistics set TBLSPACE_STATS to 0. Ben.
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