I can't think of a reason that it would break anything...
Regards, Hiram >From: Loren Rosen <[EMAIL PROTECTED]> >To: "[EMAIL PROTECTED]" ><[EMAIL PROTECTED]> >Subject: [JBoss-dev] jbossmq message transport times >Date: Tue, 15 Jan 2002 17:37:12 -0800 > >As a start on measuring jbossmq performance, I timed sending and >receiving a 1-kbyte nondurable mesage (in a loop to amortize JIT effects >and the like). Both client and server were on the same machine. The >average round trip time was 400 miliseconds, which is not good at all. > >Some investigation showed that most of the time was spent idling in the >message transport code. I tried a few things and eventually discovered >that explicitly setting TCPNODELAY on the sockets fixed the problem-- >round trip times dropped down to a few tens of milliseconds. > >I can certainly submit a patch with the one-line change, but before I >do-- is this really the right fix? Will it make something else worse? If >no one else has seen the same problem, perhaps it's O/S specific. I'm >testing on MacOS X, which for our purposes is just another Unix flavor >with an oddball GUI. > > >_________________________________________________________ >Do You Yahoo!? >Get your free @yahoo.com address at http://mail.yahoo.com > > >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
