[rabbitmq-discuss] RabbitMQ Latency
jose.mico at gmail.com
Wed Aug 22 22:35:40 BST 2012
On 08/20/2012 06:53 PM, Matthias Radestock wrote:
> The wireshark trace Tom submitted in another thread clearly shows a
> 40ms delay from the 'publish' going out to the 'deliver' coming back.
> And I've reproduced the same result on my machine.
> The difference could be down to Nagle (the Java client disables it by
> default; no idea what node-amqp does) or buffer flushing (the Java
> client flushes output buffers after complete commands, i.e. at the end
> of the three frames in case of a short basic.publish; no idea what
> node-amqp does), or some node-amqp/node.js weirdness.
On every benchmark that I've done on linux, I found that the Nagle
algorithm causes a delay of almost exactly 40ms.
Any TCP client which disables the Nagle algorithm will get its latency
improved at least by 20 times.
More information about the rabbitmq-discuss