<div dir="ltr">Hi All ,<div><br></div><div>Thank you for your replies.<br><div><br></div><div>I still have following question on them.�</div><div>It might be basic but I want to thoroughly understand what is the difference between pika-client and other client (like .net or erlang, Java) when it comes to such packing.�</div>
<div><br></div><div>1) As I learnt now Pika, Erlang , Java and .net clients all set TCP_NODELAY flag, which means that there is no intelligence within this clients to pack bytes together to make almost equal to MTU. Is it correct ?</div>
<div><br></div><div>2) And then in case of some clients like Erlang, Java and .net, the aggregation happens in buffer prior to hitting the O/S network layer so then why it's not the behaviour in pika-clients ?</div><div>
<br></div><div>My MTU size is set to 1500 bytes but I don't see that such agreegation happening.�</div><div><br></div><div><br></div><div>3) I can see that server does such packing while sending to consumer but still it does not fill till MTU limit. In my case I see it's just fill maximum of 204 bytes from server to consumer ( showing basic-deliver, content-body and content-header) �</div>
<div>Is this the expected behavior of rabbit server ?�</div>
<div><br></div><div>4) But I always see only individual frames (of individual methods) from client to server.</div><div><br></div><div><br></div><div>Best Regards,</div><div>Priyanki.�</div><div><br></div><div><br></div>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 19, 2013 at 5:58 PM, 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:54, Laing, Michael wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
pika sets TCP_NODELAY and does not provide an option to change it. Hence<br>
you may have small packets by design.<br>
</blockquote>
<br></div>
The server and the clients I mentioned set TCP_NODELAY too; the aggregation happens in buffers prior to hitting the O/S network layer.<div class="HOEnZb"><div class="h5"><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>
</div></div></blockquote></div><br></div>