Re: Re: Need help!! Sql to Informix Migration
Your onconfig shows that you are using the default informix configuration... if it is so then some work to do because the default instance the installer configures is just for testing purposes *** not for production ***
You have to plan your deployment, ie: The amount of ram you will dedicate to the engine, the disk structure, and a lot of things more.
When you do that Informix blow Sql_server by a lot but just then it will.
Follow the advise every one is giving and plan to read the Informix Administrator guide if you really want to bring good performace to your application.
J.
-----Original Message-----
From: "Obnoxio The Chav" <obnoxio@serendipita.com>
To: "Unholy" <dcalleja@gmail.com>
Date: Mon, 18 Apr 2005 10:22:20 +0100 (BST)
Subject: Re: Need help!! Sql to Informix Migration
Unholy said:
> Hi, I have developed a program that runs under sql Server, and it runs
> really fast...... The problem is that now, I have to change the DBMS to
> Informix.
>
> I installed Informix under W2000, and also under W2003, and with it the
> program is really slow, as much as 10 times slower than when it was
> running under SQl.
>
>
> I think that Informix should be faster, and I think that i hace to
> condigure it, but i do not have so much experience as with sql... can
> you help me??
>
> This is my ONCONFIG file
>
> #**************************************************************************
> #
> # INFORMIX SOFTWARE, INC.
> #
> # Title: onconfig.std
> # Description: Informix Dynamic Server Configuration Parameters
> #
> #**************************************************************************
>
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH C:\\IFMXDATA\\nomina\\rootdbs_dat.000> # 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 1 # Mirroring flag (Yes = 1, No = 0)
> MIRRORPATH D:\\IFMXDATA\\nomina\\rootdbs_mirr.000
> # Path for device containing mirrored
> root
> MIRROROFFSET 0 # Offset into mirrored device (Kbytes)>
> # Physical Log Configuration
>
> PHYSDBS rootdbs # Location (dbspace) of physical log
> PHYSFILE 2000 # Physical log file size (Kbytes)>
> # Logical Log Configuration
>
> LOGFILES 7 # Number of logical log files
> LOGSIZE 2000 # Logical log size (Kbytes)> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL,
> CONT)
>
> # Diagnostics
>
> MSGPATH C:\\PROGRA~1\\Informix\\nomina.log # System message log
> file path
> CONSOLE C:\\PROGRA~1\\Informix\\connomina.log # System console
> message path
>
> # To automatically backup logical logs, edit alarmprogram.bat and set
> # BACKUPLOGS=Y
> ALARMPROGRAM C:\\PROGRA~1\\Informix\\etc\\alarmprogram.bat # Alarm
> program path
> TBLSPACE_STATS 1 # Maintain tblspace statistics>
>
> # 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 \\\\.\\TAPE0 # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 10240 # 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 10240 # Max amount of data to put on log tape
> (Kbytes)>
> # Optical
>
> STAGEBLOB # Informix Dynamic Server/Optical
> staging area
> OPTICAL_LIB_PATH # Location of Optical Subsystem driver
> DLL
>
> # System Configuration
>
> SERVERNUM 1 # Unique id corresponding to a server> instance
> DBSERVERNAME nomina # Name of default Dynamic Server
> DBSERVERALIASES # List of alternate dbservernames
> NETTYPE soctcp,1,,NET # Override sqlhosts nettype parameters
> DEADLOCK_TIMEOUT 10 # 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 0 # If non-zero, limit number of cpu vps> to one
How many CPUs in your server?
> NOAGE 0 # Process aging
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors>
> # Shared Memory Parameters
>
> LOCKS 2000 # Maximum number of locks
> BUFFERS 2000 # Maximum number of shared buffers
BUFFERS 200000
> NUMAIOVPS 1 # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)
> CLEANERS 1 # Number of buffer cleaner processes
CLEANERS 11
> SHMBASE 0xc000000 # Shared memory base address
> SHMVIRTSIZE 8192 # 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 8 # Number of LRU queues
> LRU_MAX_DIRTY 60.000000 # LRU percent dirty begin cleaning> limit
> LRU_MIN_DIRTY 50.000000 # LRU percent dirty end cleaning limit
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 64 # Stack size (Kbytes)>
> # Dynamic Logging
> # DYNAMIC_LOGS:
> # 2 : server automatically add a new logical log when necessary.
> (ON)
> # 1 : notify DBA to add new logical logs when necessary. (ON)
> # 0 : cannot add logical log on the fly. (OFF)
> #
> # When dynamic logging is on, we can have higher values for
> LTXHWM/LTXEHWM,
> # because the server can add new logical logs during long transaction
> rollback.
> # However, to limit the number of new logical logs being added,
> LTXHWM/LTXEHWM
> # can be set to smaller values.
> #
> # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller
> values
> # to avoid long transaction rollback hanging the server due to lack of
> logical
> # log space, i.e. 50/60 or lower.
>
> DYNAMIC_LO