Re: Best way to config OWS on SCO box

From: "Steven L Cooper" <scooper@thecompounders.com> > >We are running SCO 5.0.4 on a 4-way (P200) Intel DG AV/3600 >Running RAID5 (yes Art, I know this is bad) w/100+ users using 4GL based >OE/IC/AR/etc. > >I have tried to "tune" the config for OLTP per suggestions from this >newgroup over the years and the good news is that is runs OK most of the >time...but I feel that it should be better than OK. Should I expect "good" >performance on this box w/OWS? > >I do not want to do anything major at this point (even if I could take the >system down!) because we are buying a bigger/faster server next week, so >any >help ya'll can give me that is "quick and dirty" to make the users happy >until I can setup the new server would be great! > >Of course any suggestions for my new server (4-way Xeon 550s) setup (I know >my logs are too big, etc.) would be great also! > >Thanks, >Steve > >Details below: >$ onstat -p> >INFORMIX-OnLine Version 7.20.UC2 -- On-Line -- Up 18:28:49 -- 112616 >Kbytes > >Profile >dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached >3086067 4180218 119925341 97.43 153417 253147 656013 76.61 > >isamtot open start read write rewrite delete commit >rollbk >20515282 455288 1903144 10703740 230826 69360 91159 51334 51 > >ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes >0 0 0 5251.65 1278.36 18 54 > >bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans >474976 87 28812323 0 0 35 25181 107350 > >ixda-RA idx-RA da-RA RA-pgsused lchwaits >1786162 34335 741556 2541548 16452 > >$ onstat -m> >INFORMIX-OnLine Version 7.20.UC2 -- On-Line -- Up 18:29:10 -- 112616 >Kbytes > >Message Log File: /inxsys/informix/etc/online.log > >06:27:39 Logical Log 360 Complete. >06:39:33 Checkpoint Completed: duration was 3 seconds. >07:25:04 Checkpoint Completed: duration was 4 seconds. >08:10:33 Checkpoint Completed: duration was 2 seconds. >08:56:03 Checkpoint Completed: duration was 2 seconds. >09:36:17 Logical Log 361 Complete. >09:41:38 Checkpoint Completed: duration was 6 seconds. >10:27:09 Checkpoint Completed: duration was 3 seconds. >11:00:31 Checkpoint Completed: duration was 4 seconds. >11:25:19 Checkpoint Completed: duration was 5 seconds. >12:08:00 Checkpoint Completed: duration was 4 seconds. >12:38:12 Logical Log 362 Complete. >12:53:11 Checkpoint Completed: duration was 5 seconds. >13:38:19 Checkpoint Completed: duration was 4 seconds. >14:06:01 Checkpoint Completed: duration was 5 seconds. >14:35:52 Checkpoint Completed: duration was 7 seconds. >15:07:35 Checkpoint Completed: duration was 4 seconds. >15:23:21 Logical Log 363 Complete. >15:36:22 Checkpoint Completed: duration was 5 seconds. *I* think your checkpoints are too long. Suggestions follow... >$ onstat -F> >INFORMIX-OnLine Version 7.20.UC2 -- On-Line -- Up 18:30:37 -- 112616 >Kbytes > > >Fg Writes LRU Writes Chunk Writes >9 102908 1633 This probably means you need more LRUS. >address flusher state data >11c38448 0 I 0 = 0X0 >11c3887c 1 I 0 = 0X0 >11c38cb0 2 I 0 = 0X0 >11c390e4 3 I 0 = 0X0 >11c39518 4 I 0 = 0X0 >11c3994c 5 I 0 = 0X0 >11c39d80 6 I 0 = 0X0 >11c3a1b4 7 I 0 = 0X0 >11c3a5e8 8 I 0 = 0X0 >11c3aa1c 9 I 0 = 0X0 >11c3ae50 10 I 0 = 0X0 >11c3b284 11 I 0 = 0X0 >11c3b6b8 12 I 0 = 0X0 >11c3baec 13 I 0 = 0X0 >11c3bf20 14 I 0 = 0X0 >11c3c354 15 I 0 = 0X0 > states: Exit Idle Chunk Lru > >Here is my config: >#************************************************************************** ># ># INFORMIX SOFTWARE, INC. ># ># Title: onconfig.ows ># Description: INFORMIX-OnLine Configuration Parameters ># >#************************************************************************** > ># Root Dbspace Configuration > >ROOTNAME rootdbs # Root dbspace name>ROOTPATH dev/data/ROOTDATA.DS Huh? How can you have a relative rootdbs path? >ROOTOFFSET 0 # Offset of root dbspace into device >(Kbytes) >ROOTSIZE 300000 # Size of root dbspace (Kbytes)> ># Disk Mirroring Configuration Parameters > >MIRROR 0 # Mirroring flag (Yes = 1, No = 0) >MIRRORPATH /data2/IFMXDATA/pcca/ROOTMIRR.000 >MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> ># Physical Log Configuration > >PHYSDBS rootdbs # Location (dbspace) of physical log >PHYSFILE 5000 # Physical log file size (Kbytes)> ># Logical Log Configuration > >LOGFILES 9 # Number of logical log files >LOGSIZE 18000 # Logical log size (Kbytes)> ># Diagnostics > >MSGPATH /inxsys/informix/etc/online.log # System message log file >path >CONSOLE /dev/tty02 # System console message path >ALARMPROGRAM /inxsys/informix/etc/log_full.sh # Alarm program path> ># System Archive Tape Device > >TAPEDEV /dev/rStp0 >TAPEBLK 20 # Tape block size (Kbytes) >TAPESIZE 3999999 # Maximum amount of data to put on tape >(Kbytes)> ># Log Archive Tape Device > >LTAPEDEV /dev/null Errrr....nope. Don't like this much. >LTAPEBLK 20 # Log tape block size (Kbytes) >LTAPESIZE 3999999 # Max amount of data to put on log tape >(Kbytes)> ># Optical > >STAGEBLOB # INFORMIX-OnLine/Optical staging area > ># System Configuration > >SERVERNUM 0 # Unique id corresponding to a OnLine>instance >DBSERVERNAME pcca # Name of default database server >DBSERVERALIASES pcca_shm # List of alternate dbservernames >NETTYPE tlitcp,1,150,NET >NETTYPE ipcshm,1,150,CPU >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 Make this 1 >NUMCPUVPS 1 # Number of user (cpu) vps Make this 4. >SINGLE_CPU_VP 0 # 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 20000 # Maximum number of locks@@NL