RE: Config for new live system
Posted in 2004
Ditto on Keith's comments about the LRU config. If you are going to
configure that many buffers I think you need a lot more LRUs to manage them
and more CLEANERS to flush them. And the MIN and MAX dirty are way too
high. You could be looking at some very long checkpoints and high bufwaits
if this is a busy system. Try a google search on "LRU configuration Kagel"
for some interesting reading.
Regards,
Bill
> -----Original Message-----
> From: Neil Truby [SMTP:neil.truby@ardenta.com]
> Sent: Friday, September 17, 2004 3:28 AM
> To: informix-list@iiug.org
> Subject: Config for new live system
>
> I'm implementing a brand new system for a brand new Informix customer
> soon.
> It's an on-line gambling system so it will be up for months on end.
>
>
>
> It's to be IDS 7.31FC6 on a Sun SureFire v440 with 2 processors and
> 4GBytes
> of RAM, running Solaris 9. The Informix database will be the only thing
> running, and will be replicated via HDR to an identically-configured
> server.
>
>
>
> The database server is expected only to grow to 50Gbytes. The SureFire
> v440
> has 4 x 36GBytes disks, and a StorEdge arrears, to be presented as JBOD,
> has
> an additional 8 x 36Gbyte disks. I'm planning to use two of the internal
> disks as a RAID-1 mirror boot, and use Solaris Volume Manager to present
> the
> remaining 10 as a 5 x 36 = 180 Gbyte logical volume, also protected with
> RAID-1.
>
>
>
> It'll be up for months on end so I need to get the initial config correct.
> I'd be grateful for any comments on the above layout or the proposed
> onconfig below. btw, we'll be backing up data and logs with onbar/ISM.
>
>
>
> thanks
>
> Neil
>
>
>
> #*************************************************************************
> *
> #
> # INFORMIX SOFTWARE, INC.
> #
> # Title: onconfig.std
> # Description: Informix Dynamic Server Configuration Parameters
> #
> #*************************************************************************
> *
>
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name> ROOTPATH /opt/informix/dbspaces1/rootdbs
> # 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 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 102294 # Physical log file size (Kbytes)>
> # Logical Log Configuration
>
> LOGFILES 40 # Number of logical log files
> LOGSIZE 1024 # Logical log size (Kbytes)>
> # Diagnostics
>
> MSGPATH /opt/informix/online_1.log # System message log file path
> CONSOLE /opt/informix/console_1.log # System console message path
> ALARMPROGRAM /opt/informix/7.31/etc/log_full.sh # Alarm program path
> SYSALARMPROGRAM /opt/informix/7.31/etc/evidence.sh # System Alarm program
> path
> TBLSPACE_STATS 1>
> # System Archive Tape Device
>
> TAPEDEV /opt/informix/dbspaces1/tapedev
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 2048000 # Maximum amount of data to put on tape
> (Kbytes)>
> # Log Archive Tape Device
>
> LTAPEDEV /opt/informix/dbspaces1/ltapedev # 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
>
> # System Configuration
>
> SERVERNUM 1 # Unique id corresponding to a Dynamic> Server instance
> DBSERVERNAME fafdb1_tcp # Name of default database server
> DBSERVERALIASES fafdb1_shm # List of alternate dbservernames
> NETTYPE tlitcp,2,100,NET
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
> env.
> RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
>
> MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor
> NUMCPUVPS 2 # Number of user (cpu) vps
> SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to> one
>
> NOAGE 1 # Process aging
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors>
> # Shared Memory Parameters
>
> LOCKS 50000 # Maximum number of locks
> BUFFERS 1024000 # Maximum number of shared buffers
> NUMAIOVPS 2 # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 60 # Maximum number of logical log files
> CLEANERS 29 # Number of buffer cleaner processes
> SHMBASE 0x10a000000 # Shared memory base address
> SHMVIRTSIZE 768000 # initial virtual shared memory segment> size
> SHMADD 81920 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
> 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 32 # Number of LRU queues
> LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
> LTXHWM 50 # Long transaction high water mark> percentage
> LTXEHWM 60 # Long transaction high water mark
> (exclusive)
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 64 # Stack size (Kbytes)>
> # 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
> # DRAUTO: 0 manual, 1 retain type, 2 reverse type
> DRAUTO 0 # DR automatic switchover
> DRINTERVAL 30