[rabbitmq-discuss] Question on packing of Bytes into Ethernet Frame for AMQP protocol

Michael Klishin mklishin at gopivotal.com
Mon Aug 19 16:10:31 BST 2013

Priyanki Vashi:

> I wanted to understand little bit more about AMQP, rabbitmq and pika client capability of packing of AMQP bytes into one single ethernet frames before transmission through ethernet connectivity.
> 1) What is the default behavior of pika clients and rabbit server when it comes to packing of bytes into one single ethernet frame ?
> For now I see that there is no packing done at all when I took trace on server side and I see individual frames for content-header (87bytes), content-body (137 bytes), basic.publish (87bytes) and basic- ack (87 bytes) so this makes total of 4 AMQP frames for 1 message and all four are just having a very small size.
> 2) Can we change this ? and if yes, how to change it  on server side? 
> 3) Does python-pika client supports such packing of bytes ? if yes, how to do achieve that also ? 

Both clients and RabbitMQ itself use sockets and are not aware Ethernet framing, MTU size value
used, et cetera. MTU size can be configured [1] but it's dangerous and no necessary 99% of the time.

1. http://www.debianhelp.co.uk/mtu.htm

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130819/7b083d22/attachment.pgp>

More information about the rabbitmq-discuss mailing list