<div dir="ltr">pika sets TCP_NODELAY and does not provide an option to change it. Hence you may have small packets by design.<div><br></div><div>ml</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 19, 2013 at 11:36 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 19/08/13 16:10, Michael Klishin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Both clients and RabbitMQ itself use sockets and are not aware<br>
Ethernet framing, MTU size value used, et cetera. MTU size can be<br>
configured [1] but it's dangerous and no necessary 99% of the time.<br>
</blockquote>
<br></div>
The RabbitMQ server and Java, Erlang and .net clients pass all the AMQP frames associated with content-bearing methods - i.e. the method, header and body frames - to the network layer before flushing the socket, so all these AMQP frames should generally only get split over multiple ethernet frames when exceeding the MTU size.<br>
<br>
Matthias.<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</blockquote></div><br></div>