<div class="gmail_quote">On Fri, May 25, 2012 at 5:12 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":1aj">In <span class="il">the</span> mean time, I wonder whether 500 consumers and prefetch-count of 2 is what you really want. Normally I would expect a configuration like that when you expect to take some time to process each message, but it sounds like you're going fast enough that either 500 consumers are not needed, or prefetch-count > 2 might lead to better performance.</div>
</blockquote></div><br><div>I didn't know that a larger prefetch count could reduce broker workload. �Per-message processing in this system is sometimes high (up to 20s), but it averages very low. �It's likely that 500 is overkill, but probably only by 2x or so.</div>
<div><br></div><div>Assuming a constant throughput of about 6K/sec and at least 250 workers, what prefetch seems more helpful, IYO? �10? �20?</div><div><br></div>