[rabbitmq-discuss] Disable Per-Connection Flow Control

Dwayne Campbell dwaynecampbell13 at gmail.com
Sat Oct 13 02:16:10 BST 2012


Thank you very much for your reply.


Using HIPE compilation reduced the flow control significantly.I now get
flow controlled at around 4.1 MB/S to 7.2 MB/S .However flow control
 seems to steadily remain on at 3.8MB/s for the rest of the time RabbitMQ

Each message is about approximately 300 bytes at most 800 bytes

Multiple connections(independent applications) will be made from the same
host to the RabbitMQ Server. Each connection will be sending small messages
really fast to the broker(RabbitMQ Server)****

** **

What optimizations can be made to increase throughput on RabbitMQ Server or
 the routing part of the pipeline ? Would cluster be the next option to
evaluate ?

** **

** **
Is there any output that i can gather to analyze which part of
the pipeline is the bottleneck ?



On Fri, Oct 12, 2012 at 7:14 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 11/10/12 13:14, Dwayne Campbell wrote:
>> Hi Guys,
>> RabbitMQ now turns on flow control often even at 1.5 MB/s.  I have read
>> before to increase the TCP buffer size, however I do not have access to
>> increase the TCP buffer size o the machines.
>> How can i disable Per-Connection Flow Control ?   Memory based  and Disk
>> based control is enough for me.
> Hi. You should be aware that the flow control is indicating that some part
> of the message pipeline is overloaded. If you were to turn off flow control
> it would just lead to messages backing up ahead of that part of the
> pipeline - leading to memory use ballooning very rapidly and no increase in
> throughput.
> If you are sending lots of tiny messages then the routing part of the
> pipeline can be the most expensive - my workstation manages only about
> 2.5MB/s with zero-length messages.
> The advice about increasing the buffer size is to allow your machine to
> handle short bursts of messages, at higher rates than it can manage in a
> steady state. It won't get you a higher steady state rate.
> To process messages faster on a single machine you might enable HiPE
> compilation: see http://www.rabbitmq.com/**configure.html<http://www.rabbitmq.com/configure.html>
> Cheers, Simon
> --
> Simon MacMullen
> RabbitMQ, VMware
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121012/216aea06/attachment.htm>

More information about the rabbitmq-discuss mailing list