Re: Questions on INFORMIX 7.13 and CPU VPs

sujata_soman_at_omm-la2-infotech-001@internet.omm.com wrote: > 1. Is it true that we can configure only one NETTYPE connection on the > CPU VP ? Currently, both my NETTYPE connections ( SOC and SHM ) are > configured on CPU VPs. If my assumption is true, does INFORMIX > automatically force the second NETTYPE connection to a NET vp ? Yes. > 2. I expect about 400 connections through shared memory and 200 > through SOC. Which of the connections should be configured through CPU > VP ? The ODS Performance guide suggests that if # of connections > > 350, then performance would be improved by assigning a NET VP to it. > Any comments ?? I'd go with 3 x 150 ipcshm on CPU VP's, and 2 x 100 soctcp on NET VP's. If CPU system times increases as the load over the network increases, I'd set up two different ports for listening (even with only one network adapter); sockets are quite slow to set up and the listen queue can gro quite fast. > 3. An onstat -g sch shows some of my CPU VPs to be a whole lot more > busy than the others. What determines the usage of a CPU VP ? > If you have some CPU VP's bounded to shared memory attachment, then thery are going to show more activity than the rest. It's completely normal. If all your CPU VP's are either bounded to shm/tcp or unbouded (all your connections come via NET VP's) then the average load should be more or less the same, and slightly higher on the lower numbered ones. If you have CPU VP's which are constantly idle, drop them. It's a good idea to have all your CPU VP's churning along, i.e. have a few but doing a lot :-) > 5. Okay, I am going to cheat again and ask another non-CPU VP question > onstat -g ioq , shows me a Queue named "kio". I do not think that> this is related to the KAIO. Matter of fact, the total number of these > queues seems to equal the NUMCPUVPS. Comments ?? Actually that is Kernel Asynchronous I/O. Those CPU VP's start automatically if your platform supports Kernel AIO and you will have one thread for each CPU VP in the system. In that case, you should reduce the number of AIO VP's to one (the minimum) because you will not be using them anyway. There is no way of changing how many KIO threads start, there will always be one for each CPU VP. -- Ernesto Hern'ndez-Novich - emhn@telcel.net.ve Just another Unix/Perl/Java hacker. One thing is to be the best, and another is to be the most popular. Unix: Live free or die!