Re: msc vp - more io/s than i'm used to

Check to see if you have recent changed the option field in the sqlhost file (the last column). This can have an impact on how many system calls are processed for each connection. John Miller Manoj Mohan wrote: > By system calls which require larger stack we mean calls like > gethosbyaddr/name etc. as well... > and I am sure we hit those calls normally.. > > So, if you always used to observe MSC VP then you should have seen this > normally as well.. I don't think changing > poll thread to use NET VP instead of CPU VP should cause this.. . > > Manoj > Inactive hide details for "Andrew Ford" <aford@networkip.net>"Andrew > Ford" <aford@networkip.net> > > > *"Andrew Ford" <aford@networkip.net>* > Sent by: informix-list-bounces@iiug.org > > 05/29/2008 09:41 AM > > > > To > > <informix-list@iiug.org> > > cc > > > Subject > > msc vp - more io/s than i'm used to > > > > > Hello Y'all, > > IDS 10.00.UC5 - Red Hat EL 3 > > I'm looking at my onstat -g iov output and see that the micellaneous vp > is doing work, I'm not used to seeing this. > > IBM Informix Dynamic Server Version 10.00.UC5 -- On-Line (Prim) -- > Up 1 days 06:51:31 -- 1125252 Kbytes > > AIO I/O vps:> class/vp s io/s totalops dskread dskwrite dskcopy wakeups io/wup > errors > kio 0 i 44.0 213430 194379 19051 0 499294 0.4 0 > kio 1 s 90.8 440710 426365 14345 0 1044377 0.4 0 > kio 2 i 29.1 141048 125881 15167 0 331360 0.4 0 > kio 3 i 8.8 42524 31808 10716 0 94044 0.5 0 > msc 0 i 24.3 117747 0 0 0 111544 1.1 0 > aio 0 i 0.0 231 82 0 0 231 1.0 0 > aio 1 i 0.0 0 0 0 0 0 0.0 0 > pio 0 i 0.0 0 0 0 0 0 0.0 0 > lio 0 i 0.0 0 0 0 0 0 0.0 0 > > 2 things have happened recently. > > We changed our NETTYPE parameters to get around to the APAR IC50796 THE > TCP POLL THREAD CAN DEADLOCK WAITING ON NSF.LOCK MUTEX bug > we were running into > > Previous settings > > NETTYPE soctcp,2,200,NET > NETTYPE ipcshm,4,25,CPU> > Current settings > > NETTYPE soctcp,1,400,NET > NETTYPE ipcshm,1,25,CPU> > and > > We recently switched HDR Primaries via the hdrmkpri.sh and hdrmksec.sh > scripts. > > onstat -g stk for the msc vp 0 thread always looks like this> > IBM Informix Dynamic Server Version 10.00.UC5 -- On-Line (Prim) -- > Up 1 days 06:59:28 -- 1125252 Kbytes> > Stack for thread: 5 msc vp 0> base: 0x69409000 > len: 135168 > pc: 0x0877eaca > tos: 0x69429ef0 > state: sleeping > vp: 9 > > 0x0877eaca (oninit)yield_processor_mvp(0xffffffff, 0x693f3884, > 0x483ebe5a, 0x693ff968, 0x0, 0x693ff968) > 0x08789858 (oninit)iowork (0x693f39c8, 0x693ff968, 0x7, 0x0, 0x0, 0x0) > 0x0877f1c4 (oninit)startup (0x28, 0x6942c138, 0x693fffa0, 0x2138, > 0xd282e211, 0x0) > 0x00000000 (*nosymtab*)0x0 > > > No complaints of performance problems and I don't see any negative > impact because of this, mostly just curious as to what the msc vp > could be doing. > > The documentation gives only this for msc vp: Services requests for > system calls that require a very large stack. > > That should tell me something, could going from 2 net vps to 1 net vp > cause that 1 net vp to require a larger stack for the system > call to check the socket for new data? > > Thanks, > > Andrew > > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >