[rabbitmq-discuss] Connection alwalys is blocked!

[Simon MacMullen]

Ultimately, if flow control is restricting you to 600 messages/s then 
that's the maximum rate that something (probably the disk - these are 
persistent messages?) can handle.

The reason you can't turn flow control off is that it wouldn't lead to a 
good outcome - you'd be able to publish messages to the server faster 
for a short while, but these messages would queue up internally 
(probably waiting to get on disk) and memory use would go through the 
roof. It's possible for memory to run out quite quickly in this sort of 
scenario, and you'd not be aware anything was wrong since the messages 
wouldn't count as in the queues yet.

Flow control is the messenger. Don't shoot it.

Cheers, Simon

On 04/12/13 04:00, pierre wrote:
> Hi:
>     Forgive my poor english.
>     When publishing rate is up to 600(one connection, one channel),
> connection state will be flow(publish rate recently restrict by server).
>      In cluster and ha environment, publishing rate is slower...
>
>       / <http://www.rabbitmq.com/memory.html> A per-connection mechanism that
> prevents messages being published faster than they can be routed to queues.
>      A global mechanism that prevents any messages from being published when
> the memory usage exceeds a configured threshold or free disk space drops
> below a configured threshold./
>
>      It looks like that a per-connection mechanism can not be configured or
> disabled.
>
>      Is there any better solution to imporve throughtput? How do id disable
> the flow-control?
>
>
>
>
>
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/Connection-alwalys-is-blocked-tp31807.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>


-- 
Simon MacMullen
RabbitMQ, Pivotal