Note to self: Turn off the “run slow” flag
(home)It is amazing what a single line can do.
socket.setTcpNoDelay( true );
Adding that after the creation of each socket in the brand new “jsop” binding for jaRTI yielded some amazing results when running it against a small federation I’ve been using for testing.
Before:
- OS X (intel) - 6 seconds
- OS X (ppc) - don’t even ask
- Windows (intel) - 80 seconds
- Linux (intel) - 80 seconds
After:
- OS X (intel) - 1 second
- OS X (ppc) - didn’t bother
- Windows (intel) - 3 seconds
- Linux (intel) - 3 seconds
For more information on why, see here.
Big ups to my home boy Sir Tuderlot for keeping me company during the 6 hours I spent banging head against wall and running between 600 different computers for testing purposes trying to figure that one out.

May 2nd, 2006 at 2:14 pm
I’ve hit this before too. Be careful though - the cases where this is beneficial are sensitive to a lot of environmental conditions (number of clients, message size, message rate, network settings, etc).
May 2nd, 2006 at 3:00 pm
Yeah, it makes me slightly uneasy having to change that sort of stuff, especially when the problem seemed so OS dependant, however, in this case it’s the difference between acceptable and waaaaaaaay not
May 3rd, 2006 at 1:01 am
The frustrating thing is that Nagle is right, and you really shouldn’t need to worry about this kind of thing these days. I’m curious how many of these TCP/IP odditites aren’t even issues in v6.