RE: iReach bad performance
Posted in 2000
Topics: Performance & Tuning, Server Administration, Platform-Specific Issues
Post the onconfig file and the hardware on the Sun Server. I hope you did more to tune the instance then increase the number of buffers ;). Wayne E. Martin Informix Database Administrator Kmart Corp. -----Original Message----- From: Thomas Parsli [mailto:thomas.parsli@startsiden.no] Sent: Thursday, April 13, 2000 7:05 AM To: informix-list@iiug.org Subject: Re: iReach bad performance "Poul Pedersen" <pp@q8.dk> writes: > Hi, > > I have just ported my local intranet from IIS on a Windows NT 4.0 server to > iReach on a SUN Ultra Enterprice > 3500 with Solaris 2.6. I am using the IPlanet web server from Netscape and > the drivernsapi35.so to connect to the > Informix OnLine version 9.14.uc6. I have allocated 82Mb of memory to the > Informix OnLine server (BUFFERS=20480). > > My problem is, that the iReach solutions performance is bad. To load my main > intranet page the iReach solution > takes 4 sec. On IIS the main page is ready in fractions of a second. > > What can I do to increase the performance ? Have you done UPDATE STATISTICS? Thomas
Hi Martin and thanks for your email.
Yes I tryed to increase the number of buffers from 20480 to 100000, but it
did not change the responce time.
The machine is a SUN Enterprice 3500 with 4 CPU's and 2.5Gb memory. The
disks are A5000 boxes with dual optical interfaces. The disks are striped
and mirrored.
Regards
Poul Pedersen
#**************************************************************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.std
# Description: INFORMIX-Universal Server Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME tb80root1dbs # Root dbspace nameROOTPATH /usr/Informix/dev/tb80root1dsk
# Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 500000 # 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 tb80root1dbs # Location (dbspace) of physical log
PHYSFILE 50000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 6 # Number of logical log files
LOGSIZE 20480 # Logical log size (Kbytes)
# Diagnostics
MSGPATH /usr/Informix2/tb80.log # System message log file path
CONSOLE /usr/Informix2/tb80.con # System console message path
ALARMPROGRAM /usr/Informix2/etc/log_full.sh # Alarm program path
# System Archive Tape Device
#TAPEDEV /dev/rmt/0 # Tape device path
TAPEDEV /usr/Informix2/dev/tb80arc.tape
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 20000000 # Maximum amount of data to put on tape
(Kbytes)
# Log Archive Tape Device
LTAPEDEV /dev/null # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 2000000 # Max amount of data to put on log tape
(Kbytes)
# Optical
STAGEBLOB # INFORMIX-OnLine/Universal Server staging
area
# System Configuration
SERVERNUM 80 # Unique id corresponding to a OnLineinstance
DBSERVERNAME tb80 # Name of default database server
DBSERVERALIASES tb80shm # 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)
MULTIPROCESSOR 0 # 0 for single-processor, 1 formulti-processor
NUMCPUVPS 0 # Number of user (cpu) vps# Lajo 01-03-2000 We do only have ONE CPU !!!
#SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to
one
SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps toone
NOAGE 1 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
# Lajo 01/03-2000 - Uses WAY TO MUCH MEMORY on Alhena!!!
#LOCKS 20000 # Maximum number of locks
#BUFFERS 50000 # Maximum number of shared buffers
LOCKS 32768 # Maximum number of locks
BUFFERS 100000 # Maximum number of shared buffers
NUMAIOVPS # Number of IO vps
PHYSBUFF 1024 # Physical log buffer size (Kbytes)
LOGBUFF 1024 # Logical log buffer size (Kbytes)LOGSMAX 50 # Maximum number of logical log files
CLEANERS 8 # Number of buffer cleaner processes
SHMBASE 0xa000000 # Shared memory base address#SHMBASE 0xa000000 # Shared memory base address
SHMVIRTSIZE 32768 # initial virtual shared memory segment size
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL 3600 # Check point interval (in sec)
LRUS 8 # Number of LRU queues
LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit
LTXHWM 50 # Long transaction high water markpercentage
LTXEHWM 60 # Long transaction high water mark
(exclusive)
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)
# System Page Size
# BUFFSIZE - OnLine no longer supports this configuration parameter.
# To determine the page size used by OnLine 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 worker threads
# Data Replication Variables
# DRAUTO: 0 manual, 1 retain type, 2 reverse type
DRAUTO 0 # DR automatic switchover
DRINTERVAL 30 # DR max time between DR buffer flushes (in
sec)
DRTIMEOUT 30 # DR network timeout (in sec)DRLOSTFOUND /usr/Informix2/etc/dr.lostfound # DR lost+found file path
# Backup/Restore variables
BAR_ACT_LOG /tmp/bar_act.log
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31
# Read Ahead Variables
RA_PAGES # Number of pages to attempt to read ahead
RA_THRESHOLD # Number of pages left before next group
# DBSPACETEMP:
# OnLine equivalent of DBTEMP for SE. This is the list of dbspaces
# that the OnLine SQL Engine will use to create temp tables etc.
# If specified it must be a colon separated list of dbspaces that exist
# when the OnLine system is brought online. If not specified, or if
# all dbspaces specified are invalid, various ad hoc queries will create
# temporary files in /tmp instead.
DBSPACETEMP tb80tmp1dbs # Default temp dbspaces# DBSPACETEMP # Default temp dbspaces
# DUMP*:
# The following parameters control the type of diagnostics information which
# is preserved when an unanticipated error condition (assertion failure)
occurs
# during OnLine operations.
# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
DUMPDIR /tmp # Preserve diagnostics in this directory
DUMPSHMEM 1 # Dump a copy of shared memory
DUMPGCORE 0 # Dump a
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