<br><br><div class="gmail_quote">On Mon, Feb 15, 2010 at 12:51 PM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net">matthew@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, Feb 15, 2010 at 12:47:19PM -0800, scott w wrote:<br>
> Ok thanks. I will update to tip and also update erlang. You mention all the<br>
> channels were blocked. Is there a way to up the # channels?<br>
<br>
</div>Err yes. Make more channels in the client. </blockquote><div><br>Nevermind I was thinking of something else.<br><br>�</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
But the blocking of publishers<br>
is a global thing, in order to stop Rabbit running out of memory, and to<br>
give it a chance to process load. You really have no choice but to sit<br>
it out. I would recommend you try and measure the throughput you're<br>
getting out of your disk drives. There may be some tuning that can be<br>
done there (or just throw more hardware at the problem).<br></blockquote><div><br>Ok thanks for the info.<br><br>cheers,<br>Scott<br></div></div>