Re: Single CPU Performance Problems?

Hi, I think someone in newsgroup with a better experience in performance tuning will give you more help, but I will try to give you some advices basing on my understanding of this problem. First of all, could you tell what kind of logging are you using in the database (buffered,unbuffered, no logging)? Are you using the same logging mode on MS SQL and Informix servers ? In any case I would try to play with the following parameters: 1. Check that checkpoints are not occurring too often (if it does happen - increase the physical log size). Your physical log has just 1M. It is too low in my opinion. 2. I would try increasing the logical logs number/size. 3. Try increasing the buffers number - you have configured a very low value for your server (just 10M). Try starting at 40000 (80M). May be it should be set for a larger value. 4. Check out your read ahead parameters. Are you sure they are 32/32? It seems strange to me. Try setting them at, let's say 32/16. Check out 'onstat -p' output for RA-pgused. These parameters shouldn't have a very big impact on write performance, but if you have indexes and some referential integrity constraints it could improve the performance. Of course there could be improvements to your Java program. I don't know what kind of transaction control are you using (i.e. are you loading the whole bunch of data in one transaction or not). Also if you are using JDBC2.0 you could try using batch updates to increase the performance. Best Regards, Octav On Tue, Sep 28, 1999 at 03:10:28PM -0600, Gregory P. Schin wrote: > Hi, > > I need some help tuning a single processor Sun Microsystems Ultra 5 > system with 256 meg of memory running IDS 7.3 and Solaris 7. We have an > application written in Java that frequently loads large amounts of data > into the database. We can not seem to get reliably good performance > from this application with IDS on the Sun Platform. The application > also is being run on Windows NT Server 4.0 with SQL Server 7.0 and we > get good performance. As a comparison, loading the same data on an NT > box with 1 Pentium III 400 cpu and 256 meg of memory we can average > loading 10 rows per second into the database - on the Sun box with IDS > 7.3 we can only average 3.5 rows per second. I think we should be able > to get the performance to at least equal the NT box. Any ideas or > suggestions? > > Thanks, > > Greg > > #************************************************************************** > > # > # INFORMIX SOFTWARE, INC. > # > # Title: onconfig.std > # Description: Informix Dynamic Server Configuration Parameters > # > #************************************************************************** > > # Root Dbspace Configuration > > ROOTNAME rootdbs # Root dbspace name> ROOTPATH /dev/informix_root # Path for device containing root dbspace > ROOTOFFSET 2 # Offset of root dbspace into device (Kbytes) > ROOTSIZE 20000 # 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 1000 # Physical log file size (Kbytes)> > # Logical Log Configuration > > LOGFILES 6 # Number of logical log files > LOGSIZE 500 # Logical log size (Kbytes)> > # Diagnostics > > MSGPATH /usr/informix/online.log # System message log file path > CONSOLE /dev/console # System console message path > # ALARMPROGRAM /usr/informix/etc/log_full.sh # Alarm program path > ALARMPROGRAM /usr/informix/etc/no_log.sh # Alarm program path> SYSALARMPROGRAM /usr/informix/etc/evidence.sh # System Alarm program > path > TBLSPACE_STATS 0> > # System Archive Tape Device > > # TAPEDEV /dev/tapedev # Tape device path > TAPEDEV /dev/null # 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 /dev/tapedev # 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 > > # System Configuration > > SERVERNUM 0 # Unique id corresponding to a Dynamic Server instance > DBSERVERNAME engledive # Name of default database server > DBSERVERALIASES # engledive_tp # List of alternate dbservernames > NETTYPE # Configure poll thread(s) for nettype > DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env. > RESIDENT 1 # 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> > # Shared Memory Parameters > > LOCKS 20000 # Maximum number of locks > BUFFERS 5000 # Maximum number of shared buffers > NUMAIOVPS 2 # Number of IO vps > PHYSBUFF 32 # Physical log buffer size (Kbytes) > LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 6 # Maximum number of logical log files > CLEANERS 8 # Number of buffer cleaner processes > SHMBASE # Shared memory base address > SHMVIRTSIZE 8000 # 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 # LRU percent dirty begin cleaning limit > LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit > LTXHWM 50 # Long transaction high water mark percentage > LTXEHWM 60 # Long transaction high water mark (exclusive) > TXTIMEOUT 300 # Transaction timeout (in sec) > STACKSIZE 32 # Stack size (Kbytes)> > # System Page Size > # BUFFSIZE - Dynamic Server no longer supports this configuration > parameter. > # To determine the page size used by Dynamic Server 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 /usr/informix/etc/dr.lostfound # DR lost+found file path> > # CDR Variables > CDR_LOGBUFFERS 2048 # size o