aquino.gustavo at gmail.com
Mon May 10 03:58:02 BST 2010
On Sun, May 9, 2010 at 7:08 PM, Martin Sustrik <sustrik at 250bpm.com> wrote:
> Gustavo Aquino wrote:
>> On Sun, May 9, 2010 at 6:02 PM, Martin Sustrik <sustrik at 250bpm.com<mailto:
>> sustrik at 250bpm.com>> wrote:
>> Thanks but today we are trying to get this information by this
>> hard way. I'm trying to get a help here, someone may have done
>> it before or RabbitMQ owners can have this number and will help
>> me to get back time loosed hacking packages network.
>> Per-message overhead for AMQP/0-8 is 50+ bytes.
>> Thanks, do you know if RabbitMQ cover this pattern ?
> Sure. It's minimal size of envelope for AMQP/0-8. Actual envelope may be
> larger depending on what you put into it (exchange name, topic etc.)
Well MTU is about maximum not minimal, so you sad a interest stuff, let say
that we posting message to one exchange named "123"and it routed to one
queue named "456" on other machine, so what is MTU from primarily message
and what the size of second ?
>> This number is very important, and have significant differences
>> between AMQP implementations. Just for example the Qpid package
>> have a oversize in message larger than RabbitMQ until you can
>> send 32k messages per second using 100mbps you can do only 16k
>> messages per second with Qpid with the same 100mbps. (Messages
>> with 213bytes).
>> Resuming If you will have a high throughput and need high
>> performance make sure that you will not want to use jumbo frame.
>> It's very unlikely that MTU size setting will have any impact on
>> performance in your scenario.
>> If you use jumbo frame you have a significant impact in your round trip,
>> and make sure we are working to save microseconds/nanoseconds and a simple
>> overhead in round trip message impact us so much.
>> Again the MTU question is to do some calc to refine our network
>> configurations, not a simple configuration in Ethernet interface, a network
>> admin use this calc to project your network to a specific requirement, and
>> when you are talking in microseconds/nanoseconds this configuration made a
>> big difference. For example we are getting bad performance in one of our
>> nodes, and we discovered that router was configured for 576 MTU the result
>> is an overhead of 0.500 us each message with one specific throughput.
> 0.5 us is presumably less than 1% of overall latency. In fact, it's pretty
> hard even to measure that kind of latency difference. Just the latency
> jitter is going to be many times higher than that.
> What exactly are you trying to achieve? And what are you measuring?
Look 0.5us in each message based on a throughput, whats happend if your
router have a 576 MTU and your other are sending 1.500 MTU? it will
fragmente this packages in 3 packages of 576 MTU, this cause something like
a full network bandwidth used, in other words if my router can use only
1.500 MTU how much messages I can put in this value ? this is te basic calc
that we want do do and about that we need to know the MTU of RabbitMQ
messages understand ?
If RabbitMQ are receiving 20 messages per millisecond from publisher and
each message have 213 bytes, what the size of packages over network to a
consumer or other broker?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss