I really like the peer transport in ActiveMQ. It seems to be just the kind of setup we need. However, we do have low round-trip latency requirements in some applications. I was seeing unacceptably bad latencies (~200ms) for synchronous round trips. I installed Wireshark and performed network analysis to see what was going on. It appeared to be a Nagle algorithm / TCP ACK delay issue. Essentially, after the first message request and reply, the next request message may be delayed while waiting for a delayed ACK from the other broker. This should be resolvable by enabling tcpNoDelay. However, the peer transport URI provides no mechanism to enable tcpNoDelay. In fact, I went into the source code and found that the TCP network connecter specified in the PeerTransportFactory is hard coded to tcp://localhost:0. Basically, I need a way to turn on tcpNoDelay in peer transport. Thanks.
Andrew Steele -- View this message in context: http://www.nabble.com/I-need-a-way-to-set-tcpNoDelay-on-peer-transport-TCP-network-connections-tf3137715.html#a8695603 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
