HP IDS 7.3 Performance problems.
Kimberly Dicken <infosys@ecke.com> wrote in message
news:01bf11bd$78013760$66c8c8c8@KDicken...
> Our HP D260 w/2 CPU and 512MB memory running 10.2 is dragging.
>
> Dragging is the only word for it. It has moments of brilliance, but
> otherwise just slogs along.
>
> Our application is in 4GL and running against IDS 7.3 UC3. ONSTAT -U run
> with about 35-45 active users. 90% are local users running on the HP
> itself. We occasionally have a PC user here or there that connects to the
> DB.
>
> We've had it for coming close to a year now, after transitioning from a
old
> G50.
>
> Running OnLine 5.x on the G50 was as fast or faster as the D260. It was
> rarely slower. And it wasn't as consistently slow. And our G50 had the DB
> on a single drive.
>
> Our HP Guy(tm) seems to want to do nothing except a) throw RAM at the
> problem, and/or b) throw disks at the problem. I'm not completely
confident
> that the problem is solely I/O as the new machine has more disks, and
> better controllers. Backups are 15 minutes.
>
> We currently have the DBMS scattered across 3 drives with rootdbs, logdbs,
> and tempdbs on one drive, and the data split up across dbspace1 and
> dbspace2. All of these drives are mirrored using HPs mirroring.
>
> Informix is currently using 30000 buffers, and a SHMVIRTSIZE of 60000. It
> is my understanding that HPUX doesn't like having more than 2 or 3 shared
> memory segments, otherwise its performance goes way down. Now, I don't
know
> if this is a system limitation, or process limitation as to how many
> segments the process is attached to. According to ipcs, informix owns 2,
> and the system has 7 total segments.
>
> I've followed the update statistics suggestions from the performance guide
> (that was rather involved). I've also got the environment variable
NO_SUBQF
> = 1 set. That helped some queries out immensely.
>
> I've only got one CPU configured. Checkpoints are running about every five
> minutes, and hit for roughly 3-5 seconds (though there have been some
> spikes of 10-20 seconds).
>
> Read cache is running about 98% and the write cache around 86%.
>
> I've included my ONCONFIG file, but stripped the extraneous comments. If
> anyone can point out the GO FAST switch I need to flip, I'd appreciate the
> pointer.
>
> Any thoughts are welcome.
>
> Thanx!
Will ! Check your 'onstat -P' - if Btree percentage is too high you probably
run in to Informix with incorrect index compressing.
>
> Will Hartung
>
> ----------8<--------------------8<--------------8<--------------
> ROOTNAME rootdbs # Root dbspace name> ROOTPATH /dev/informix/rootdbs # Path for device containing root
> dbspace
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 102400 # Size of root dbspace (Kbytes)> MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
> MIRRORPATH # Path for device containing mirrored root
> MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> PHYSDBS rootdbs # Location (dbspace) of physical log
> PHYSFILE 1000 # Physical log file size (Kbytes)
> LOGFILES 10 # Number of logical log files
> LOGSIZE 20000 # Logical log size (Kbytes)> MSGPATH /usr2/informix/online.log # System message log file path
> CONSOLE /dev/console # System console message path
> ALARMPROGRAM /usr2/informix/etc/log_full.sh # Alarm program path> SYSALARMPROGRAM /usr2/informix/etc/evidence.sh # System Alarm program path
> TBLSPACE_STATS 1Set this to 0. Or you need this statistics ?
> TAPEDEV /dev/rmt/0m # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 12000000 # Maximum amount of data to put on tape
> (Kbytes)
> LTAPEDEV /dev/null # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE 10240 # Max amount of data to put on log tape
> (Kbytes)> STAGEBLOB # Informix Dynamic Server/Optical staging
> area
> SERVERNUM 0 # Unique id corresponding to a Dynamic> Server instance
> DBSERVERNAME shm_xena # Name of default database server
> DBSERVERALIASES tcp_xena # List of alternate dbservernames
> NETTYPE soctcp,10,10,CPU # Configure poll thread(s) for nettype
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
> env.
> RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
Set this to 1
> MULTIPROCESSOR 0 # 0 for single-processor, 1 for> multi-processor
> NUMCPUVPS 1 # Number of user (cpu) vps
> SINGLE_CPU_VP 1 # 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
> LOCKS 50000 # Maximum number of locks
> BUFFERS 30000 # Maximum number of shared buffers
> NUMAIOVPS # Number of IO vps
Oh ! If KAIO is not used, set this to at minimum 5 for your number of disks.
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 20 # Maximum number of logical log files
> CLEANERS 4 # Number of buffer cleaner processes
> SHMBASE 0x0 # Shared memory base address
> SHMVIRTSIZE 60000 # initial virtual shared memory segment> size
> SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
> 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 4 # Number of LRU queues
For 32000 buffers it's too low. Try 24. Respectively increase CLEANERS to
about 25.
> LRU_MAX_DIRTY 7 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 5 # 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 32 # Stack size (Kbytes)
> OFF_RECVRY_THREADS 10 # Default number of offline worker> threads
> ON_RECVRY_THREADS 1 # Default number of online workerthreads
> DRAUTO 0 # DR automatic switchover
> DRINTERVAL 30 # DR max time between DR buffer flushes
(in
> sec)
> DRTIMEOUT 30 # DR network timeout (in sec)
> DRLOSTFOUND /dev/null # DR lost+found file path> CDR_LOGBUFFERS 2048 # size of log reading buffer pool (Kbytes)
> CDR_EVALTHREADS 1,2 # evaluator threads
(per-cpu-vp,additional)> CDR_DSLOCKWA
Our HP D260 w/2 CPU and 512MB memory running 10.2 is dragging.
Dragging is the only word for it. It has moments of brilliance, but
otherwise just slogs along.
Our application is in 4GL and running against IDS 7.3 UC3. ONSTAT -U run
with about 35-45 active users. 90% are local users running on the HP
itself. We occasionally have a PC user here or there that connects to the
DB.
We've had it for coming close to a year now, after transitioning from a old
G50.
Running OnLine 5.x on the G50 was as fast or faster as the D260. It was
rarely slower. And it wasn't as consistently slow. And our G50 had the DB
on a single drive.
Our HP Guy(tm) seems to want to do nothing except a) throw RAM at the
problem, and/or b) throw disks at the problem. I'm not completely confident
that the problem is solely I/O as the new machine has more disks, and
better controllers. Backups are 15 minutes.
We currently have the DBMS scattered across 3 drives with rootdbs, logdbs,
and tempdbs on one drive, and the data split up across dbspace1 and
dbspace2. All of these drives are mirrored using HPs mirroring.
Informix is currently using 30000 buffers, and a SHMVIRTSIZE of 60000. It
is my understanding that HPUX doesn't like having more than 2 or 3 shared
memory segments, otherwise its performance goes way down. Now, I don't know
if this is a system limitation, or process limitation as to how many
segments the process is attached to. According to ipcs, informix owns 2,
and the system has 7 total segments.
I've followed the update statistics suggestions from the performance guide
(that was rather involved). I've also got the environment variable NO_SUBQF
= 1 set. That helped some queries out immensely.
I've only got one CPU configured. Checkpoints are running about every five
minutes, and hit for roughly 3-5 seconds (though there have been some
spikes of 10-20 seconds).
Read cache is running about 98% and the write cache around 86%.
I've included my ONCONFIG file, but stripped the extraneous comments. If
anyone can point out the GO FAST switch I need to flip, I'd appreciate the
pointer.
Any thoughts are welcome.
Thanx!
Will Hartung
----------8<--------------------8<--------------8<--------------
ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/informix/rootdbs # Path for device containing root
dbspace
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 102400 # Size of root dbspace (Kbytes)MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH # Path for device containing mirrored root
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)PHYSDBS rootdbs # Location (dbspace) of physical log
PHYSFILE 1000 # Physical log file size (Kbytes)
LOGFILES 10 # Number of logical log files
LOGSIZE 20000 # Logical log size (Kbytes)MSGPATH /usr2/informix/online.log # System message log file path
CONSOLE /dev/console # System console message path
ALARMPROGRAM /usr2/informix/etc/log_full.sh # Alarm program pathSYSALARMPROGRAM /usr2/informix/etc/evidence.sh # System Alarm program path
TBLSPACE_STATS 1
TAPEDEV /dev/rmt/0m # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 12000000 # Maximum amount of data to put on tape
(Kbytes)
LTAPEDEV /dev/null # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 10240 # Max amount of data to put on log tape
(Kbytes)STAGEBLOB # Informix Dynamic Server/Optical staging
area
SERVERNUM 0 # Unique id corresponding to a DynamicServer instance
DBSERVERNAME shm_xena # Name of default database server
DBSERVERALIASES tcp_xena # List of alternate dbservernames
NETTYPE soctcp,10,10,CPU # Configure poll thread(s) for nettype
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 1 # Number of user (cpu) vps
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
LOCKS 50000 # Maximum number of locks
BUFFERS 30000 # Maximum number of shared buffers
NUMAIOVPS # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 20 # Maximum number of logical log files
CLEANERS 4 # Number of buffer cleaner processes
SHMBASE 0x0 # Shared memory base address
SHMVIRTSIZE 60000 # initial virtual shared memory segmentsize
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
LRUS 4 # Number of LRU queues
LRU_MAX_DIRTY 7 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 5 # 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)
OFF_RECVRY_THREADS 10 # Default number of offline workerthreads
ON_RECVRY_THREADS 1 # Default number of online worker threads
DRAUTO 0 # DR automatic switchover
DRINTERVAL 30 # DR max time between DR buffer flushes (in
sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND /dev/null # DR lost+found file pathCDR_LOGBUFFERS 2048 # size of log reading buffer pool (Kbytes)
CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR
queue (Kbytes)
BAR_ACT_LOG /tmp/bar_act.log
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31ISM_DATA_POOL ISMData # If the data pool name is changed, be sure
to
ISM_LOG_POOL ISMLogs
RA_PAGES # Number of pages to attempt to read ahead
RA_THRESHOLD # Number of pages left before next group
DBSPACETEMP tempdbs # Default temp dbspaces
DUMPDIR /tmp # Preserve diagnostics in this directory
DUMPSHMEM 1 # Dump a copy of shared memory
DUMPGCORE 0 # Dump a core image
See below . . .
Kimberly Dicken wrote:
>
> Our HP D260 w/2 CPU and 512MB memory running 10.2 is dragging.
>
> Dragging is the only word for it. It has moments of brilliance, but
> otherwise just slogs along.
>
> Our application is in 4GL and running against IDS 7.3 UC3. ONSTAT -U run
> with about 35-45 active users. 90% are local users running on the HP
> itself. We occasionally have a PC user here or there that connects to the
> DB.
>
> We've had it for coming close to a year now, after transitioning from a old
> G50.
>
> Running OnLine 5.x on the G50 was as fast or faster as the D260. It was
> rarely slower. And it wasn't as consistently slow. And our G50 had the DB
> on a single drive.
>
> Our HP Guy(tm) seems to want to do nothing except a) throw RAM at the
> problem, and/or b) throw disks at the problem. I'm not completely confident
> that the problem is solely I/O as the new machine has more disks, and
> better controllers. Backups are 15 minutes.
>
> We currently have the DBMS scattered across 3 drives with rootdbs, logdbs,
> and tempdbs on one drive, and the data split up across dbspace1 and
> dbspace2. All of these drives are mirrored using HPs mirroring.
>
This would cause a bit of a bottleneck . . . any way to spread them out
between the three drives??
> Informix is currently using 30000 buffers, and a SHMVIRTSIZE of 60000. It
> is my understanding that HPUX doesn't like having more than 2 or 3 shared
> memory segments, otherwise its performance goes way down. Now, I don't know
> if this is a system limitation, or process limitation as to how many
> segments the process is attached to. According to ipcs, informix owns 2,
> and the system has 7 total segments.
>
> I've followed the update statistics suggestions from the performance guide
> (that was rather involved). I've also got the environment variable NO_SUBQF
> = 1 set. That helped some queries out immensely.
>
> I've only got one CPU configured. Checkpoints are running about every five
> minutes, and hit for roughly 3-5 seconds (though there have been some
> spikes of 10-20 seconds).
>
> Read cache is running about 98% and the write cache around 86%.
>
> I've included my ONCONFIG file, but stripped the extraneous comments. If
> anyone can point out the GO FAST switch I need to flip, I'd appreciate the
> pointer.
>
> Any thoughts are welcome.
>
> Thanx!
>
> Will Hartung
>
> ----------8<--------------------8<--------------8<--------------
> ROOTNAME rootdbs # Root dbspace name> ROOTPATH /dev/informix/rootdbs # Path for device containing root
> dbspace
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 102400 # Size of root dbspace (Kbytes)> MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
> MIRRORPATH # Path for device containing mirrored root
> MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> PHYSDBS rootdbs # Location (dbspace) of physical log
> PHYSFILE 1000 # Physical log file size (Kbytes)
It seems that PHYSFILE should be a bit bigger.
> LOGFILES 10 # Number of logical log files
> LOGSIZE 20000 # Logical log size (Kbytes)> MSGPATH /usr2/informix/online.log # System message log file path
> CONSOLE /dev/console # System console message path
> ALARMPROGRAM /usr2/informix/etc/log_full.sh # Alarm program path> SYSALARMPROGRAM /usr2/informix/etc/evidence.sh # System Alarm program path
> TBLSPACE_STATS 1
> TAPEDEV /dev/rmt/0m # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 12000000 # Maximum amount of data to put on tape
> (Kbytes)
> LTAPEDEV /dev/null # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE 10240 # Max amount of data to put on log tape
> (Kbytes)> STAGEBLOB # Informix Dynamic Server/Optical staging
> area
> SERVERNUM 0 # Unique id corresponding to a Dynamic> Server instance
> DBSERVERNAME shm_xena # Name of default database server
> DBSERVERALIASES tcp_xena # List of alternate dbservernames
> NETTYPE soctcp,10,10,CPU # Configure poll thread(s) for nettype
> 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 for> multi-processor
> NUMCPUVPS 1 # Number of user (cpu) vps
> SINGLE_CPU_VP 1 # 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
> LOCKS 50000 # Maximum number of locks
> BUFFERS 30000 # Maximum number of shared buffers
60M buffers with 512M memory . . . I'd bump this up to 64000.
> NUMAIOVPS # Number of IO vpsAre you using HP's KAIO? We had a problem with it until we upgraded to
7.30.uc7. Might need to configure NUMAIOVPS and disable KAIO if you're
having a problem.
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 20 # Maximum number of logical log files
> CLEANERS 4 # Number of buffer cleaner processes
> SHMBASE 0x0 # Shared memory base address
> SHMVIRTSIZE 60000 # initial virtual shared memory segment> size
> SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
> 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 4 # Number of LRU queues
LRUs and CLEANERS may need to come up a bit if you're increasing
BUFFERS.
> LRU_MAX_DIRTY 7 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 5 # 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 32 # Stack size (Kbytes)
> OFF_RECVRY_THREADS 10 # Default number of offline worker> threads
> ON_RECVRY_THREADS 1 # Default number of online worker threads
> DRAUTO 0 # DR automatic switchover
> DRINTERVAL 30 # DR max time between DR buffer flushes (in
> sec)
> DRTIMEOUT 30 # DR network timeout (in sec)
> DRLOSTFOUND /dev/null # DR lost+found file path> CDR_LOGBUFFERS 2048 # size of log reading buffer pool (Kbytes)
> CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,
In article <01bf11bd$78013760$66c8c8c8@KDicken>, Kimberly Dicken
<infosys@ecke.com> writes
>Our HP D260 w/2 CPU and 512MB memory running 10.2 is dragging.
>
>Dragging is the only word for it. It has moments of brilliance, but
>otherwise just slogs along.
>
>Our application is in 4GL and running against IDS 7.3 UC3. ONSTAT -U run
Try moving to 7.31.
>with about 35-45 active users. 90% are local users running on the HP
>itself. We occasionally have a PC user here or there that connects to the
>DB.
>
>We've had it for coming close to a year now, after transitioning from a old
>G50.
>
>Running OnLine 5.x on the G50 was as fast or faster as the D260. It was
>rarely slower. And it wasn't as consistently slow. And our G50 had the DB
>on a single drive.
>
>Our HP Guy(tm) seems to want to do nothing except a) throw RAM at the
>problem, and/or b) throw disks at the problem. I'm not completely confident
>that the problem is solely I/O as the new machine has more disks, and
>better controllers. Backups are 15 minutes.
>
>We currently have the DBMS scattered across 3 drives with rootdbs, logdbs,
>and tempdbs on one drive, and the data split up across dbspace1 and
>dbspace2. All of these drives are mirrored using HPs mirroring.
>
You need
Drive 1 rootdbs + tempdbs1
Drive 2 physical log + tempdbs2
Drive 3 logical log + tempdbs3
Then stripe a datadbs across the three disks.
>Informix is currently using 30000 buffers, and a SHMVIRTSIZE of 60000. It
>is my understanding that HPUX doesn't like having more than 2 or 3 shared
>memory segments, otherwise its performance goes way down. Now, I don't know
>if this is a system limitation, or process limitation as to how many
It is a per process limitation.
>segments the process is attached to. According to ipcs, informix owns 2,
>and the system has 7 total segments.
>
>I've followed the update statistics suggestions from the performance guide
>(that was rather involved). I've also got the environment variable NO_SUBQF
>= 1 set. That helped some queries out immensely.
>
>I've only got one CPU configured. Checkpoints are running about every five
>minutes, and hit for roughly 3-5 seconds (though there have been some
>spikes of 10-20 seconds).
>
>Read cache is running about 98% and the write cache around 86%.
>
>I've included my ONCONFIG file, but stripped the extraneous comments. If
>anyone can point out the GO FAST switch I need to flip, I'd appreciate the
>pointer.
>
>Any thoughts are welcome.
>
>Thanx!
>
>Will Hartung
>
>----------8<--------------------8<--------------8<--------------
>ROOTNAME rootdbs # Root dbspace name>ROOTPATH /dev/informix/rootdbs # Path for device containing root
>dbspace
>ROOTOFFSET 0 # Offset of root dbspace into device
>(Kbytes)
>ROOTSIZE 102400 # Size of root dbspace (Kbytes)>MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
>MIRRORPATH # Path for device containing mirrored root
>MIRROROFFSET 0 # Offset into mirrored device (Kbytes)>PHYSDBS rootdbs # Location (dbspace) of physical log
Move this into a seperate dbspace on a separate disk as above
>PHYSFILE 1000 # Physical log file size (Kbytes) Increase!! What does onstat -d give? How large is your database??
>LOGFILES 10 # Number of logical log files
>LOGSIZE 20000 # Logical log size (Kbytes)>MSGPATH /usr2/informix/online.log # System message log file path
>CONSOLE /dev/console # System console message path
>ALARMPROGRAM /usr2/informix/etc/log_full.sh # Alarm program path>SYSALARMPROGRAM /usr2/informix/etc/evidence.sh # System Alarm program path
>TBLSPACE_STATS 1
>TAPEDEV /dev/rmt/0m # Tape device path
>TAPEBLK 16 # Tape block size (Kbytes)
Try increasing to 128
>TAPESIZE 12000000 # Maximum amount of data to put on tape
>(Kbytes)
>LTAPEDEV /dev/null # Log tape device path
>LTAPEBLK 16 # Log tape block size (Kbytes)
>LTAPESIZE 10240 # Max amount of data to put on log tape
>(Kbytes)>STAGEBLOB # Informix Dynamic Server/Optical staging
>area
>SERVERNUM 0 # Unique id corresponding to a Dynamic>Server instance
>DBSERVERNAME shm_xena # Name of default database server
>DBSERVERALIASES tcp_xena # List of alternate dbservernames
>NETTYPE soctcp,10,10,CPU # Configure poll thread(s) for nettype
soctcp,10,10,NET
tcp should run on a NET VP as CPU VPs cannot block hence it spends
lots of time polling the socket rather than goes to sleep on it!
>DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
>env.
>RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
RESIDENT -1
>MULTIPROCESSOR 0 # 0 for single-processor, 1 for>multi-processor
>NUMCPUVPS 1 # Number of user (cpu) vps
>SINGLE_CPU_VP 1 # 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 0 and 1 or 1 and 1 whichever works (depends upon how the CPUs are
numbered.
>LOCKS 50000 # Maximum number of locks
>BUFFERS 30000 # Maximum number of shared buffers
>NUMAIOVPS # Number of IO vps
>PHYSBUFF 32 # Physical log buffer size (Kbytes)
>LOGBUFF 32 # Logical log buffer size (Kbytes)>LOGSMAX 20 # Maximum number of logical log files
>CLEANERS 4 # Number of buffer cleaner processes
>SHMBASE 0x0 # Shared memory base address
>SHMVIRTSIZE 60000 # initial virtual shared memory segment>size
>SHMADD 8192 # Size of new shared memory segments
>(Kbytes)
>SHMTOTAL 0 # Total shared memory (Kbytes).
>0=>unlimited
>CKPTINTVL 300 # Check point interval (in sec)
>LRUS 4 # Number of LRU queues
>LRU_MAX_DIRTY 7 # LRU percent dirty begin cleaning limit
>LRU_MIN_DIRTY 5 # 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 32 # Stack size (Kbytes)
>OFF_RECVRY_THREADS 10 # Default number of offline worker>threads
>ON_RECVRY_THREADS 1 # Default number of online worker threads
>DRAUTO 0 # DR automatic switchover
>DRINTERVAL 30 # DR max time between DR buffer flushes (in
>sec)
>DRTIMEOUT 30 # DR network timeout (in sec)
>DRLOSTFOUND /dev/null # DR lost+fou