<br><br><div class="gmail_quote">On Fri, Feb 15, 2013 at 1:19 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jonathan,<div class="im"><br>
<br>
On 15/02/13 20:53, Jonathan Halterman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What I was reading was from here:<br>
<br>
<a href="http://www.rabbitmq.com/api-guide.html#consuming" target="_blank">http://www.rabbitmq.com/api-<u></u>guide.html#consuming</a><br>
<br>
"Each Channel has its own dispatch thread"<br>
</blockquote>
<br></div>
That isn't meant to imply that there is one thread per channel, though I can see how it could be read that way.<br>
<br>
Consumer processing happens on the threads in the Consumer thread pool See <a href="http://www.rabbitmq.com/api-guide.html#consumer-thread-pool" target="_blank">www.rabbitmq.com/api-guide.<u></u>html#consumer-thread-pool</a>. But processing is constrained s.t. all messages arriving on a channel are processed serially, i.e. at any point in time at most one thread in the pool is processing consumer work for a given channel.<br>
<br>
I am cc'ing my colleague Steve, who may be able to shed more light on this and what he meant by "dispatch thread" above.</blockquote><div><br></div><div>I understand, thanks for the clarification. It was just the wording of the docs led me to believe there was a separate thread per channel in addition to the consumer threadpool. Glad to know there is not!</div>
<div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br>