Prefetch Size about longears HOT 3 CLOSED

@atheriel
Hey there and great job on the library.

Is it possible for exactly 1 support on a per-consumer basis?
This is what makes the most sense for long-running work because we don't want a process to consume messages only to have them wait since it's already busy, and it removes the ability to scale by spawning more processes on demand when messages are piling up.

from longears.

Just to clarify, are you asking that it be possible to change the default (e.g. with a compile-time -DDEFAULT_PREFETCH_COUNT=1 flag), or that it be possible to change the count on a per-consumer basis?

Also, I'm very interested to hear what kind of workload you're running that this is causing issues for.

from longears.

To provide some additional context: this package uses 50 as the default because that's the number I've seen used in other clients.

My general understanding of RabbitMQ best practice at present is that (1) you never want to use the default unbounded prefetch count/size unless your consumers are stupidly fast; (2) for very consistent workloads you can carefully optimize throughput by picking "just-right" prefetch size and count values; otherwise, (3) you probably want something close to 50 or exactly 1 for true round-robin.

Using R makes (1) irrelevant and (2) suspect, so I'm guessing if you want something different than 50 you want exactly 1.

from longears.