IDS Forum

RE: Tuning IDS 7.3 TC9

Posted By: Steven Tay
Date: Wednesday, 14 November 2007, at 10:59 p.m.

In Response To: Re: Tuning IDS 7.3 TC9 (Guy .)

Hi,

I do not have any support from Informix.

My latest IDS I have is IDS 7.31 TD1, but I did not install last time.

I have not intention to upgrade to latest IDS and just want to maintain
current version or upgrade to 7.31 TD1.

Please advise.

Warmest Regards
Steven Tay

-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Guy .
Sent: Thursday, November 15, 2007 10:06 AM
To: ids@iiug.org
Subject: Re: Tuning IDS 7.3 TC9 [10371]

> NUMAIOVPS should be higher (4 recommended for
> Logging, plus one per chunk if the machine does not support KAIO).

Since this is a Windows machine it is KAIO-only so NUMAIOVPS should
typically
remain at 1 unless you are doing a lot of non-chunk writes (like to
SQEXPLAIN
files and online log).

Also consider upgrading the IDS version to take advantage of newer
performance
features and avoiding end of support for 7.31.

Guy

----- Original Message ----
From: Marcus Haarmann <marcus.haarmann@midoco.de>
To: ids@iiug.org
Sent: Wednesday, November 14, 2007 12:12:28 AM
Subject: RE: Tuning IDS 7.3 TC9 [10370]

Hi,

You could increase BUFFERS (to 100000 minimum) and NUMCPUVPS (to 4
minimum), set MULTIPROCESSOR to 1 and SINGLE_CPU_VP to 0 to make use of

the multiprocessing. NUMAIOVPS should be higher (4 recommended for
Logging, plus one per chunk if the machine does not support KAIO).
If this is a dedicated server, memory values can even be higher, but
not
until you get into swapping ;).
How many Shared memory segments are being used on the old machine
(onstat -g seg) ? If more than one in class V, increase SHMVIRTSIZE.

You should have an enormous boost just because of the processor. If you

have newer harddisks in the system (which I suppose) this should have
also a good effect.
The config you have is not very huge, so I would expect the same number

of users as on the old machine would have very good response times.
If the number of users increases at the same time, you should also
increase LOCKS, maybe STACKSIZE to 64 or 128.

Marcus

-----Original Message-----
From: TAY STEVEN [mailto:taysteven@gmail.com]
Sent: Wednesday, November 14, 2007 3:04 AM
To: ids@iiug.org
Subject: Tuning IDS 7.3 TC9 [10368]

Hi,

i am going to change the server to fast processor and more memory.

how can i customise the onconfig to performace db faster.

current server is pentium 2-450 with 512MB RAM.

new server is Xeon Quad Core 1.6 with 1GB RAM.

current onconfig setting as below...

Please help and thank you.

#***********************************************************************
***
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.std
# Description: INFORMIX-OnLine Configuration Parameters #
#***********************************************************************
***
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace name
ROOTPATH D:\IFMXDATA\ol_baan\rootdbs_dat.000 # Path for device
containing root dbspace

# Path for device containing root dbspace ROOTOFFSET 0 # Offset of root

dbspace into device (Kbytes) ROOTSIZE 20480 # 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 baandb_plog # Location (dbspace) of physical
log PHYSFILE 204800 # Physical log file size (Kbytes) # Logical Log
Configuration LOGFILES 80 # Number of logical log files LOGSIZE 5000 #
Logical log size (Kbytes) # Diagnostics MSGPATH D:\Informix\online.log
#
System message log file path CONSOLE D:\Informix\console.log # System
console message path ALARMPROGRAM # Alarm program path # System Archive

Tape Device TAPEDEV NUL # Tape device path TAPEBLK 16 # Tape block size

(Kbytes) TAPESIZE 3901084 # Maximum amount of data to put on tape
(Kbytes) # Log Archive Tape Device LTAPEDEV NUL # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes) LTAPESIZE 3901084 # Max
amount of data to put on log tape (Kbytes) # Optical STAGEBLOB ,1 #
INFORMIX-OnLine/Optical staging area # System Configuration SERVERNUM 0

# Unique id corresponding to a OnLine instance DBSERVERNAME ol_baan #
Name of default Dynamic Server DBSERVERALIASES # List of alternate
dbservernames NETTYPE soctcp,1,100,CPU # Override sqlhosts nettype
parameters 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 0 # 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 13092 # Maximum number of

shared buffers NUMAIOVPS 1 # Number of IO vps PHYSBUFF 32 # Physical
log
buffer size (Kbytes) LOGBUFF 32 # Logical log buffer size (Kbytes)
LOGSMAX 115 # Maximum number of logical log files CLEANERS 1 # Number
of
buffer cleaner processes SHMBASE 0xc000000 # Shared memory base address

SHMVIRTSIZE 32768 # initial virtual shared memory segment size SHMADD
16384 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # Total
shared memory (Kbytes). 0=>unlimited CKPTINTVL 300 # 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 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 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 \tmp # DR lost+found file path # CDR Variables
CDR_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) # Backup/Restore
variables BAR_ACT_LOG D:\Informix\bar_act.log #Path of log file for
onbar.exe BAR_MAX_BACKUP 1 BAR_RETRY 1 BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 15 # Read Ahead Variables RA_PAGES 4 # 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 baandb_tmp # 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 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 single user's session
# ADT*
# ADT* parameters moved to adtcfg file
FILLFACTOR 60 # Fill factor for building indexes # method for OnLine to

use when determining current time USEOSTIME 0 # 0: use internal
time(fast), 1: get time from OS(slow) # Parallel Database Queries (pdq)

# OFF => 0, LOW => 1, HIGH => 100
MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority DS_MAX_QUERIES 1 #
Maximum number of decision support queries DS_TOTAL_MEMORY 2048 #
Decision support memory (Kbytes) DS_MAX_SCANS 1048576 # Maximum number
of decision support scans DATASKIP off # List of dbspaces to skip #
OPTCOMPIND # 0 => Nested loop joins will be preferred (where #
possible)
over sortmerge joins and hash joins.
# 1 => If the transaction isolation mode is not # "repeatable read",
optimizer behaves as in (2) # below. Otherwise it behaves as in (0)
above.
# 2 => Use costs regardless of the transaction isolation # mode. Nested

loop joins are not necessarily # preferred. Optimizer bases its
decision
purely # on costs.
OPTCOMPIND 0 # To hint the optimizer
ONDBSPACEDOWN 0 # Dbspace down option: 0 = CONTINUE, 1 = ABORT, 2 =
WAIT
LBU_PRESERVE 0 # Preserve last log for log backup BAR_BSALIB_PATH
D:\ISM\2.20\bin\libbsa.dll # Location of ISM XBSA DLL

************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.

****************************************************************************
***
Forum Note: Use "Reply" to post a response in the discussion forum.

____________________________________________________________________________
________
Be a better pen pal.
Text or chat with friends inside Yahoo! Mail. See how.
http://overview.mail.yahoo.com/

****************************************************************************
***
Forum Note: Use "Reply" to post a response in the discussion forum.

Messages In This Thread

• Tuning IDS 7.3 TC9
  TAY STEVEN -- Tuesday, 13 November 2007, at 9:04 p.m.
  • Re: Tuning IDS 7.3 TC9
    VARTIKA AGRAWAL -- Wednesday, 14 November 2007, at 2:17 a.m.
  • RE: Tuning IDS 7.3 TC9
    Marcus Haarmann -- Wednesday, 14 November 2007, at 3:12 a.m.
    • Re: Tuning IDS 7.3 TC9
      Guy . -- Wednesday, 14 November 2007, at 9:05 p.m.
      • RE: Tuning IDS 7.3 TC9
        Steven Tay -- Wednesday, 14 November 2007, at 10:59 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.