RE: Question about IDS scalabiltiy
You should have NETTYPE parameter (2) for DBSERVERNAME and DBSERVERALIASES.
Suggest you turn Read Aheads OFF (0) until you have the system running.
Are all parameters the same as recommended in your release notes?
Murray Wood
-----Original Message-----
From: Obnoxio The Clown [SMTP:obnoxio@hotmail.com]
Sent: Thursday, May 27, 1999 2:22 AM
To: cbolden@harrahs.com; cbolden1@midsouth.rr.com; informix-list@iiug.org
Subject: RE: Question about IDS scalabiltiy
I don't remember, are you doing OLTP or DSS?
From: Carlos Bolden <cbolden@harrahs.com>
>
># Root Dbspace Configuration
See embedded comments.
>ROOTNAME rootdbs # Root dbspace name>ROOTPATH /dev/prodi/prod-100 # Path for device containing root
>dbspace
>ROOTOFFSET 0 # Offset of root dbspace into device
>(Kbytes)
>ROOTSIZE 50000 # Size of root dbspace (Kbytes)>
># Disk Mirroring Configuration Parameters
>
>MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
>
># Physical Log Configuration
>
>PHYSDBS physlog # Location (dbspace) of physical log
>PHYSFILE 200000 # Physical log file size (Kbytes)>
># Logical Log Configuration
>
>LOGFILES 40 # Number of logical log files
>LOGSIZE 1000 # Logical log size (Kbytes)>
># Diagnostics
>
>MSGPATH /opt/informix/7.3/logs/patron.log
> # System message log file path
>CONSOLE /opt/informix/7.3/logs/patron.con
> # System console message path
>ALARMPROGRAM /opt/informix/7.3/etc/log_full.sh # Alarm program path
>
># System Archive Tape Device
>
>TAPEDEV /dev/null # Tape Device path
>TAPEBLK 32 # Tape block size (Kbytes)
>TAPESIZE 35000000 # Maximum amount of data to put on tape
>(Kbytes)>
># Log Archive Tape Device
>
>LTAPEDEV /dev/null # Log tape device path
>LTAPEBLK 32 # Log tape block size (Kbytes)
>LTAPESIZE 35000000 # Max amount of data to put on log tape
>(Kbytes)>
># Optical
>
>STAGEBLOB # INFORMIX-OnLine/Optical staging area
>
># System Configuration
>
>SERVERNUM 1 # Unique id corresponding to a OnLine>instance
>DBSERVERNAME patronx # Name of default database server
>DBSERVERALIASES patronx_net # List of alternate dbservernames
>DEADLOCK_TIMEOUT 300 # Max time to wait of lock in>distributed env.
>RESIDENT 1 # Forced residency flag (Yes = 1, No =
>0)
>
>MULTIPROCESSOR 1 # 0 for single-processor, 1 for>multi-processor
>NUMCPUVPS 9 # Number of user (cpu) vps
Given that you have 32 CPUs, isn't this a bit low?
>SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps>to one
>
>NOAGE 1 # Process aging
>AFF_SPROC 1 # Affinity start processor
>AFF_NPROCS 9 # Affinity number of processors
These 3 can be dodgy, check your release notes (if you haven't already! :-)
># Shared Memory Parameters
>
>LOCKS 300000 # Maximum number of locks
>BUFFERS 40000 # Maximum number of shared buffers
This is very low.
>NUMAIOVPS 4 # Number of IO vps
You should consider upping this quite a bit. How big are your disks?
>PHYSBUFF 512 # Physical log buffer size (Kbytes)
>LOGBUFF 32 # Logical log buffer size (Kbytes)
Is your database logged?
>LOGSMAX 50 # Maximum number of logical log files
>CLEANERS 32 # Number of buffer cleaner processes
>SHMBASE 0x10000000 # Shared memory base address
>SHMVIRTSIZE 589824 # initial virtual shared memory segment>size
>SHMADD 65536 # Size of new shared memory segments
>(Kbytes)
>SHMTOTAL 839680 # Total shared memory (Kbytes).
>0=>unlimited
>CKPTINTVL 300 # Check point interval (in sec)
>LRUS 32 # Number of LRU queues
>LRU_MAX_DIRTY 3 # LRU percent dirty begin cleaning limit
>LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit
Set this to 0.
>LTXHWM 50 # Long transaction high water mark>percentage
>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 worker>threads
>ON_RECVRY_THREADS 4 # 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 /var/tmp
> # DR lost+found file path>
># Read Ahead Variables
>RA_PAGES 24 # Number of pages to attempt to read>ahead
>RA_THRESHOLD 22 # 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 temp1,temp2,temp3,temp4,temp5,temp6,temp7
> # 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 /var/tmp # Preserve diagnostics in this directory
>DUMPSHMEM 0 # Dump a copy of shared memory
>DUMPGCORE 0 # Dump a core image using 'gcore'
>DUMPCORE 0 # Dump a core image (Warning:this aborts
>OnLine)
>DUMPCNT 1 # Number of shared memory or gcore dumps>for
> # a