Re: dbaccess connect time difference between onipcshm and onsoctcp
Ya'ar Akman wrote: > We have informix database in tru64 unix that has shared memory and tcp > connection (onipcshm, onsoctcp). > > 10 connection through shm takes 20 seconds. > 10 connection through tcp takes less than 5 seconds. > > I was expecting shm would be faster, in fact it is not. > > Is there a something wrong in informix or tru64 unix configuration. I once had a similar situation, where it seemed that the server would wake up for one connection, then go to sleep again and not notice any new connections for a second or so. I don't think I ever got to the bottom of why it was happening - and I've not spotted it happening since. I don't recall whether I reconfigured anything, or rebooted anything. It would have been on Solaris (8 most likely, possibly 7) and version 9.30 or 9.40 of IDS. What are the two NETTYPE lines? Any chance you've got the shared memory working on a NET VP? How many CPU VPs do you have? Which version of IDS? Neither rate of connecting strikes me as fast - what else is the code doing? -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.01 -- http://dbi.perl.org/
t1:/>onstat -c | grep -i nettype
NETTYPE ipcshm,1,100,CPU # Override sqlhosts nettype parameters
NETTYPE soctcp,1,100,NET # Override sqlhosts nettype parameters
I have changed the VP class across the ipcshm, and soctcp. The
performance result did not change very much.
So assumed that it is very much related ipcshm and soctcp.
For the test purpuses I have run following perl script
$i=0;
while ($i< 20){
$t1=`echo "select count(*) from t_account"|dbaccess today >log
2>log`;
$i++;
}
with the following machine.
d1 machine: 2 cpu 500 Mhz Alpha tru64 unix system with some kernel
tuning
t1 machine : 1 cpu 1Ghz Alpha tru64 unix system
The test result is as following:
d1 t1
ipcshm 23 sec 39 sec
soctcp 6 sec 5 sec
There is no other load on this machine.
I was expecting t1 machine would be faster.
I think some tru64 unix parameter has also affect on this result.
I would appriciate any help.
Yasar Akman