You would set it on any Tcp speaking library you do not wish to have buffered so yes, set it on both server and client.
Sincerely, Jason On Jun 14, 2013 8:37 AM, "Rajesh Khan" <[email protected]> wrote: > Thanks for your reply do we set this option in both the sender and the > receiver > > > On Fri, Jun 14, 2013 at 1:27 AM, Jason Barto <[email protected] > >wrote: > > > Tcp no delay disables a part of the Tcp stack which essentially buffers > Tcp > > packets until there are enough to basically make the sending worthwhile. > > > > http://en.m.wikipedia.org/wiki/Nagle's_algorithm > > > > Effectively this keeps the small Tcp messages going from client to server > > or vice versa from getting there as quickly as possible as they are being > > buffered. If latency is a concern with your deployment it's best to > disable > > Nagle by setting Tcp no delay to true. > > > > Sincerely, > > Jason > > While going through the manual the only information I got was > > > > For C++ > > "For latency sensitive applications, setting tcp-nodelay on qpidd and on > > client connections can help reduce the latency". > > > > I have two questions > > 1- What tcp-nodelay do ? > > 2- Do we set it up on both the sender and the receiver ? > > > > Thanks in advance > > >
