[rabbitmq-discuss] Proposal: Change consumers Round-Robin behaviour
dave at nexttolast.com
Thu May 2 13:43:03 BST 2013
On May 2, 2013, at 7:53 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
> Does anybody who currently depends on round-robin want to speak up?
My apps don't currently strictly rely upon round-robin, but scale better with it. I have found that you can avoid the RRRRGGGG behavior by managing your prefetch size and not acking too soon.
In our app, our cluster gets huge spikes of traffic on a fixed period, and we need to evenly distribute the load across the worker cluster to keep up with realtime requirements. Round-robin in this case spreads the load better than a random distribution, as random only guarantees even distribution in the long run, where the long run is demonstrably too long for our update frequency. Since we know the volume of data and the amount of processing on each node, we can tune very accurately for cost.
I've only tested with 10s-100s of consumers on a single queue. So YMMV. Though
More information about the rabbitmq-discuss