Re: Upgrading server - Do i need to change config ?
F. LACROIX je napisao:
> "Neil Truby" <neil.truby@ardenta.com> a écrit dans le message de news:
> 4i96mgF2jfl9U1@individual.net...
> > "F. LACROIX" <soft @ datacolfrance.com> wrote in message
> > news:44bf5959$0$891$ba4acef3@news.orange.fr...
> >> Hello,
> >>
> >> I was running IDS 7.31 on a quite old PIII 800 with 1Go RAM, my boss
> >> agreed few days ago to replace this old server by a brand new one ... an
> >> HP Proliant ML350, with Xeon processor and 2go RAM.
> >>
> >> Do i need to make change to my onconfig to optimize this new power ?
> >>
> >> I made test already and some very long quering are done now in about half
> >> the time. Can i best those results ?
> >>
> >> Thanks for your answers.
> >>
> >> F. LACROIX
> >> DATACOL France.
> >>
> >> NB : i am not a confirmed informix administrator, so write as if i was 4
> >> year old :-)
> >
> > If the server is used mainly for Informix, and you have added no new
> > applications to it, then you can probably afford to increase the BUFFERS
> > parameter and see if it impoves your read and write cache rates.
> >
> > Why not post your current $ONCONFIG file, and the results from onstat -p
> > and onstat -g iov on the new system?
> >
> > And tell us the new OS - presume SuSE or RH Linux?
> >
>
> Hi,
>
> The main use for the server is Informix.
>
> I must confess that even if i am of more than average skill in programming,
> i am well below in system. I kept the same OS ... Win 2000 ... first because
> i knew how to install it, and 2ndly, because i know near to nothing about
> Linux ... shame on me :-)
>
> i will post the onconfig below, but as the new system is not yet on-line (we
> still work on the old one) i dont know if the onstat file will be of use ...
>
> Many thanks for you help.
>
> F. LACROIX
> DATACOL France
>
I do not have a lot of experience with Informix for Windows (Unix/Linux
are my platforms for IDS), but I will try to give some hints. I hope
someone will correct me if I am wrong.
> -----------------------------------------------------
> ONCONFIG
> -----------------------------------------------------
> #**************************************************************************
> #
> # INFORMIX SOFTWARE, INC.
> #
> # Title: onconfig.std
> # Description: Informix Dynamic Server Configuration Parameters
> #
> #**************************************************************************
>
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH d:\\IFMXDATA\\ol_srvprecix\\rootdbs_dat.000 # Path for device> containing root dbspace
> ROOTOFFSET 4 # Offset of root dbspace into device (Kbytes)
> ROOTSIZE 500000 # 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 rootdbs # Location (dbspace) of physical log
> PHYSFILE 10000 # Physical log file size (Kbytes)>
> # Logical Log Configuration
>
> LOGFILES 30 # Number of logical log files
> LOGSIZE 2000 # Logical log size (Kbytes)
I would suggest larger logs and more of them. You could locate them in
their separate dbspace.
> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT)
>
> # Diagnostics
>
> MSGPATH d:\\Usr\\Informix\\ol_srvprecix.log # System message log file path
> CONSOLE d:\\Usr\\Informix\\conol_srvprecix.log # System console message path
> ALARMPROGRAM # Alarm program path>
> # System Diagnostic Script.
> # SYSALARMPROGRAM - Full path of the system diagnostic script (e.g.
> # c:\\informix\\etc\\evidence.bat.) Set this parameter
> # if you want a different Diagnostic Script than
> # {INFORMIXDIR}\\etc\\evidence.bat, which is default.
>
> # System Archive Tape Device
>
> TAPEDEV k:\\IFMXBKUP\\ifmxbkup.bak # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 2000000 # 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 150000 #10240 # Max amount of data to put on log tape
> (Kbytes)>
You may test if speed of tape operations grows with larger bock sizes
(say 32 or 64 KB).
> # Optical
>
> STAGEBLOB # Informix Dynamic Server/Optical staging
> area
> OPTICAL_LIB_PATH # Location of Optical Subsystem driver DLL
>
> # System Configuration
>
> SERVERNUM 0 # Unique id corresponding to a server instance> stance
> DBSERVERNAME ol_srvprecix # Name of default Dynamic Server
> DBSERVERALIASES # List of alternate dbservernames
> NETTYPE onsoctcp,1,,NET # 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
>
To be able to use fast CPU to the max, you may need to set these 3
parameters in a manner like:
MULTIPROCESSOR 1
NUMCPUVPS 2 (or 3?)
SINGLE_CPU_VP 0
> NOAGE 0 # Process aging
I am not sure for Windows. For Solaris, NOAGE must be set to 1 to use
the CPU properly.
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors>
> # Shared Memory Parameters
>
> LOCKS 600000 # Maximum number of locks
> BUFFERS 50000 # Maximum number of shared buffers
With 2 GB of RAM, you could set at least 150000. If I remember well at
Windows the page size is 4 KB, so that would mean about 600 GB.
> NUMAIOVPS 1 # Number of IO vps
This number should be probably larger. For example, 31.
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 40 # Maximum number of logical log files
Increase this.
> CLEANERS 1 # Number of buffer cleaner processes
The number of cleaners should probably correspond to the number of LRUs
(with a factor of 1 or 2).
> SHMBASE 0x20000000L # Shared memory base address
> SHMVIRTSIZE 8192 # initial virtual shared memory segment size
> SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
The two SHM parameters should be much larger (SMHVIRTSIZE in undreds of
MB, SHMADD at least in dozens of MB)..
> SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 50 # Number of LRU queues
> LRU_MAX_DIRTY 5 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 3 # LRU percent dirty end cleaning limit
> LTXHWM 50 # Long transaction high water mark pe
Hi,
Thanks for your answer, as our new server will not be in use until
september, i will look into the documentation to see how to make the change
you suggested. I have weeks to experiment ... and to re-install everything
if something goes wrong :-)
F. LACROIX
DATACOL France
"darko" <darko.krstic@gmail.com> a 'crit dans le message de news:
1153476888.554464.286550@i42g2000cwa.googlegroups.com...
F. LACROIX je napisao:
> "Neil Truby" <neil.truby@ardenta.com> a 'crit dans le message de news:
> 4i96mgF2jfl9U1@individual.net...
> > "F. LACROIX" <soft @ datacolfrance.com> wrote in message
> > news:44bf5959$0$891$ba4acef3@news.orange.fr...
> >> Hello,
> >>
> >> I was running IDS 7.31 on a quite old PIII 800 with 1Go RAM, my boss
> >> agreed few days ago to replace this old server by a brand new one ...
> >> an
> >> HP Proliant ML350, with Xeon processor and 2go RAM.
> >>
> >> Do i need to make change to my onconfig to optimize this new power ?
> >>
> >> I made test already and some very long quering are done now in about
> >> half
> >> the time. Can i best those results ?
> >>
> >> Thanks for your answers.
> >>
> >> F. LACROIX
> >> DATACOL France.
> >>
> >> NB : i am not a confirmed informix administrator, so write as if i was
> >> 4
> >> year old :-)
> >
> > If the server is used mainly for Informix, and you have added no new
> > applications to it, then you can probably afford to increase the BUFFERS
> > parameter and see if it impoves your read and write cache rates.
> >
> > Why not post your current $ONCONFIG file, and the results from onstat -p
> > and onstat -g iov on the new system?
> >
> > And tell us the new OS - presume SuSE or RH Linux?
> >
>
> Hi,
>
> The main use for the server is Informix.
>
> I must confess that even if i am of more than average skill in
> programming,
> i am well below in system. I kept the same OS ... Win 2000 ... first
> because
> i knew how to install it, and 2ndly, because i know near to nothing about
> Linux ... shame on me :-)
>
> i will post the onconfig below, but as the new system is not yet on-line
> (we
> still work on the old one) i dont know if the onstat file will be of use
> ...
>
> Many thanks for you help.
>
> F. LACROIX
> DATACOL France
>
I do not have a lot of experience with Informix for Windows (Unix/Linux
are my platforms for IDS), but I will try to give some hints. I hope
someone will correct me if I am wrong.
> -----------------------------------------------------
> ONCONFIG
> -----------------------------------------------------
> #**************************************************************************
> #
> # INFORMIX SOFTWARE, INC.
> #
> # Title: onconfig.std
> # Description: Informix Dynamic Server Configuration Parameters
> #
> #**************************************************************************
>
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH d:\\IFMXDATA\\ol_srvprecix\\rootdbs_dat.000 # Path for device> containing root dbspace
> ROOTOFFSET 4 # Offset of root dbspace into device (Kbytes)
> ROOTSIZE 500000 # 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 rootdbs # Location (dbspace) of physical log
> PHYSFILE 10000 # Physical log file size (Kbytes)>
> # Logical Log Configuration
>
> LOGFILES 30 # Number of logical log files
> LOGSIZE 2000 # Logical log size (Kbytes)
I would suggest larger logs and more of them. You could locate them in
their separate dbspace.
> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT)
>
> # Diagnostics
>
> MSGPATH d:\\Usr\\Informix\\ol_srvprecix.log # System message log file path
> CONSOLE d:\\Usr\\Informix\\conol_srvprecix.log # System console message path
> ALARMPROGRAM # Alarm program path>
> # System Diagnostic Script.
> # SYSALARMPROGRAM - Full path of the system diagnostic script (e.g.
> # c:\\informix\\etc\\evidence.bat.) Set this parameter
> # if you want a different Diagnostic Script than
> # {INFORMIXDIR}\\etc\\evidence.bat, which is default.
>
> # System Archive Tape Device
>
> TAPEDEV k:\\IFMXBKUP\\ifmxbkup.bak # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 2000000 # 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 150000 #10240 # Max amount of data to put on log tape
> (Kbytes)>
You may test if speed of tape operations grows with larger bock sizes
(say 32 or 64 KB).
> # Optical
>
> STAGEBLOB # Informix Dynamic Server/Optical staging
> area
> OPTICAL_LIB_PATH # Location of Optical Subsystem driver DLL
>
> # System Configuration
>
> SERVERNUM 0 # Unique id corresponding to a server instance> stance
> DBSERVERNAME ol_srvprecix # Name of default Dynamic Server
> DBSERVERALIASES # List of alternate dbservernames
> NETTYPE onsoctcp,1,,NET # 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
>
To be able to use fast CPU to the max, you may need to set these 3
parameters in a manner like:
MULTIPROCESSOR 1
NUMCPUVPS 2 (or 3?)
SINGLE_CPU_VP 0
> NOAGE 0 # Process aging
I am not sure for Windows. For Solaris, NOAGE must be set to 1 to use
the CPU properly.
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors>
> # Shared Memory Parameters
>
> LOCKS 600000 # Maximum number of locks
> BUFFERS 50000 # Maximum number of shared buffers
With 2 GB of RAM, you could set at least 150000. If I remember well at
Windows the page size is 4 KB, so that would mean about 600 GB.
> NUMAIOVPS 1 # Number of IO vps
This number should be probably larger. For example, 31.
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 40 # Maximum number of logical log files
Increase this.
> CLEANERS 1 # Number of buffer cleaner processes
The number of cleaners should probably correspond to the number of LRUs
(with a factor of 1 or 2).
> SHMBASE 0x20000000L # Shared memory base address
> SHMVIRTSIZE 8192 # initial virtual shared memory segment size
> SHMADD 8192 # Size of new shared memory segment