Re: OnLine and Baan IV

From: "Fergus Hayne" <ferg@gusweb.demon.co.uk> > >I have recently taken over administration of an HP-UX / Informix / Baan >site. I am looking for any suggestions for ways to improve the general >configuration / performance of the database. Get rid of Baan, for a start... :-) >Briefly we have a K460 database server 3 processors, 3 Gb memory, 2 >autoraid >each with 12 * 9.1Gb. Might want a few more CPUs? >There are two instances of OnLine on the server. There are 6 client HP >servers referencing the main database server. > >Baan IV runs on all servers and connects to the database server using its >own proprietory database driver. > >Does anyone else out there use Baan IV and Online 7.22.UC3 > >I have attached the configuration info from one of the large instance, the >other is set up similarly. > >The system is very badly fragmented currently as the default values for the >extent sizes have been used !!! > >I will fix this over the next few decades! >INFORMIX-OnLine Version 7.22.UC3 -- On-Line -- Up 20:46:10 -- 850912 >Kbytes > > ># System Configuration > >SERVERNUM 0 # Unique id corresponding to a OnLine>instance >DBSERVERNAME bbrlgld1 # Name of default database server >DBSERVERALIASES # List of alternate dbservernames >NETTYPE soctcp,1,300,CPU # Configure poll thread(s) for nettype You _might_ get some benefit from splitting this over 2 CPUs. >RESIDENT 0 # Forced residency flag (Yes = 1, No = 0) This should be set to 1. >MULTIPROCESSOR 1 # 0 for single-processor, 1 for>multi-processor >NUMCPUVPS 2 # Number of user (cpu) vps >SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to>one > >NOAGE 0 # Process aging You might want to set this to 1. >AFF_SPROC 0 # Affinity start processor >AFF_NPROCS 0 # Affinity number of processors You might want to affinity one (or two) CPU(s). ># Shared Memory Parameters > >LOCKS 200000 # Maximum number of locks >BUFFERS 150000 # Maximum number of shared buffers >NUMAIOVPS 6 # Number of IO vps Are you using KAIO? If not, you will want more of these. >PHYSBUFF 64 # Physical log buffer size (Kbytes) >LOGBUFF 64 # Logical log buffer size (Kbytes) If you're using buffered logging, you might get some benefit from tweaking these. >LOGSMAX 1000 # Maximum number of logical log files >CLEANERS 6 # Number of buffer cleaner processes >SHMBASE 0x0 # Shared memory base address >SHMVIRTSIZE 500000 # initial virtual shared memory segment>size If onstat -g seg shows more than one V-segment, you should increase this. >LRUS 8 # Number of LRU queues You'll probably want to move this up a bit. To say, 127? :-) >LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit >LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit> ># Read Ahead Variables >RA_PAGES # Number of pages to attempt to read ahead >RA_THRESHOLD # Number of pages left before next group You _might_ get some benfit from tweaking these. HTH. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com