On Fri, 2013-06-14 at 08:45 +0100, Jason Barto wrote: > 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.
You should note that for the forthcoming 0.24 release and forward tcp-nodelay is the default for both C++ client and broker. See https://issues.apache.org/jira/browse/QPID-3689 It turned out that for nearly every case tcp-nodelay gives as good or better throughput as well as latency. Obviously you should benchmark as you would in any case. You can turn tcp-nodelay OFF for the broker by using a config file - the line there would be "tcp-nodelay=false" OR by setting QPID_TCP_NODELAY=0 in the environment of the running broker. At the client end tcp-nodelay is a connection option in the messaging API. Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
