Onconfig parameters tuning

Onconfig parameters tuning

Post by Kokane Rajesh, IB » Fri, 08 Feb 2002 14:00:10



This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C1AF94.521D92D8
Content-Type: text/plain

Hi,

We have configured new server for legacy application and transferred 2
instances from old server to this server.  It has 128 MB memory and 1 cpu. I
am attaching here onconfig file of one instance. I want to tune informix
onconfig parameter to improve the performance.

OS :- Sco Openserver 5
Informix :- informix ver 5

Pls revert back if you need any additional info. <<ban>>

Kindly help me.

Thanks & Regards

Rajesh Kokane
IGSI

------_=_NextPart_000_01C1AF94.521D92D8
Content-Type: application/octet-stream;
        name="ban.log"
Content-Disposition: attachment;
        filename="ban.log"
Content-Description: ban

$ pg tbconfig.ban
ROOTNAME        rootdbs         # Root dbspace name
ROOTPATH        /dev/raw1       # Path for device containing root dbspace
ROOTOFFSET      450002          # Offset of root dbspace into device (Kbytes)
ROOTSIZE        100000          # Size of root dbspace (Kbytes)
MIRROR          0               # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH                      # Path for device containing root dbspace mirror
MIRROROFFSET    0               # Offset into mirror device (Kbytes)
PHYSDBS         rootdbs         # Name of dbspace that contains physical log
PHYSFILE        20000           # Physical log file size (Kbytes)
LOGFILES        5              # Number of logical log files
LOGSIZE         10000           # Size of each logical log file (Kbytes)
MSGPATH         /usr1/informix/banonline.log # OnLine message log pathname
CONSOLE         /dev/console    # System console message pathname
TAPEDEV         /dev/null       # Archive tape device pathname
TAPEBLK         16              # Archive tape block size (Kbytes)
TAPESIZE        2000000         # Max amount of data to put on tape (Kbytes)
LTAPEDEV        /dev/null       # Logical log tape device pathname
LTAPEBLK        16              # Logical log tape block size (Kbytes)
LTAPESIZE       2000000         # Max amount of data to put on log tape (Kbytes)
SERVERNUM       2               # Unique id associated with this OnLine instance
DBSERVERNAME    kwstars          # Unique name of this OnLine instance
RESIDENT        0               # Forced residency flag (Yes = 1, No = 0)
USERS           10              # Maximum number of concurrent user processes
TRANSACTIONS    80              # Maximum number of concurrent transactions
LOCKS           5000            # Maximum number of locks
BUFFERS         2000            # Maximum number of shared memory buffers
TBLSPACES       800             # Maximum number of active tblspaces
CHUNKS          8               # Maximum number of chunks
DBSPACES        8               # Maximum number of dbspaces and blobspaces
PHYSBUFF        64              # Size of physical log buffers (Kbytes)
LOGBUFF         64              # Size of logical log buffers (Kbytes)
LOGSMAX         50              # Maximum number of logical log files
CLEANERS        0               # Number of page-cleaner processes
SHMBASE         0x0               # Shared memory base address
CKPTINTVL       300             # Checkpoint interval (in seconds)
LRUS            8               # Number of LRU queues
LRU_MAX_DIRTY   60              # LRU modified begin-cleaning limit (percent)
LRU_MIN_DIRTY   50              # LRU modified end-cleaning limit (percent)
LTXHWM          80              # Long TX high-water mark (percent)
LTXEHWM         90              # Long TX exclusive high-water mark (percent)
DYNSHMSZ        0               # Dynamic shared memory size (Kbytes)
GTRID_CMP_SZ    32              # Number of bytes to use in GTRID comparision
DEADLOCK_TIMEOUT 60              # Max time to wait for lock in distributed env.
TXTIMEOUT       300             # Transaction timeout for I-STAR (in seconds)
SPINCNT         0               # No. of times process tries for latch
STAGEBLOB                       # Reserved for INFORMIX-OnLine/Optical
BUFFSIZE        2048            # Page size (do not change!)

------_=_NextPart_000_01C1AF94.521D92D8--

 
 
 

Onconfig parameters tuning

Post by Tsutomu Ogiwar » Sat, 09 Feb 2002 14:39:31


Hi Kokane.

I think, BUFFERS is too low.
Increase BUFFERS , for example 200000.
And CLEANERS > 0.

BTW.
Decrease LTXHWM and LTXEHWM.
LTXHWM 50.
LTXEHWM 60.

Regards.


Quote:>Hi,

>We have configured new server for legacy application and transferred 2
>instances from old server to this server.  It has 128 MB memory and 1 cpu. I
>am attaching here onconfig file of one instance. I want to tune informix
>onconfig parameter to improve the performance.

>OS :- Sco Openserver 5
>Informix :- informix ver 5

>Pls revert back if you need any additional info. <<ban>>

>Kindly help me.

>Thanks & Regards

>Rajesh Kokane
>IGSI

--
Tsutomu Ogiwara

INFORMIX PROFESSIONAL SERVICES
DATABASE BUSINESS DEPT.
ITOCHU TECHNO-SCIENCE Corporation
KURITA-KUDAN BLDG., 1-11-15, FUJIMI,
CHIYODA-KU TOKYO,102-0074 JAPAN


 
 
 

Onconfig parameters tuning

Post by Andrew Ham » Tue, 12 Feb 2002 09:36:03



>Hi Kokane.

>I think, BUFFERS is too low.
>Increase BUFFERS , for example 200000.
>And CLEANERS > 0.


>>We have configured new server for legacy application and transferred 2
>>instances from old server to this server.  It has 128 MB memory and 1 cpu.
I
>>am attaching here onconfig file of one instance. I want to tune informix
>>onconfig parameter to improve the performance.

You are suggesting 400Mb of buffers on a 128 MB machine? In which case, I
suggest you bump up the memory on the box to at least 512Mb, preferably
768mb.
 
 
 

Onconfig parameters tuning

Post by Tsutomu Ogiwar » Wed, 13 Feb 2002 13:21:53


Hi Andrew.

Yes, you are right.
Sorry...

Make a correction, 200000 -> 38000.

Regards.



>>Hi Kokane.

>>I think, BUFFERS is too low.
>>Increase BUFFERS , for example 200000.
>>And CLEANERS > 0.


>>>We have configured new server for legacy application and transferred 2
>>>instances from old server to this server.  It has 128 MB memory and 1 cpu.
>I
>>>am attaching here onconfig file of one instance. I want to tune informix
>>>onconfig parameter to improve the performance.

>You are suggesting 400Mb of buffers on a 128 MB machine? In which case, I
>suggest you bump up the memory on the box to at least 512Mb, preferably
>768mb.

--
Tsutomu Ogiwara

INFORMIX PROFESSIONAL SERVICES
DATABASE BUSINESS DEPT.
ITOCHU TECHNO-SCIENCE Corporation
KURITA-KUDAN BLDG., 1-11-15, FUJIMI,
CHIYODA-KU TOKYO,102-0074 JAPAN

 
 
 

1. SCO Kernel Parameters and Onconfig parameters

I am currently setting up an instance of IDS 7.3 workgroup on a SCO 5.05
platform. We will probably have at most 25 users connected to a transaction
logged database. I am looking for a good reference for proper kernel and
Onconfig settings for a setup like this. The server that I will use will
have a minimum of 1 gig of ram and a single one gigahertz processor. I have
some kernel settings that a former employee where I work had obtained. I
don't know where he got these parameters from and I don't know if they are
correct.

I also want to make sure that I am setting up some of the parameters in
Onconfig correctly. I have gotten several instances up and running, but have
not tested them under a heavy user load.

2. how determine unused space for indexes

3. Onconfig Tuning Guide

4. T-SQL stored procedure authoring tools

5. onconfig tuning

6. Save / Cancel

7. onconfig parameters

8. 13505-ID-Idaho-DBA Skills-ORACLE Financials-ORACLE-Database Administrator

9. ONCONFIG parameters

10. Onconfig parameter

11. FW: 3 onconfig parameter questions, help