Hi Matthias,<br><br><div class="gmail_quote">On Wed, Oct 7, 2009 at 2:24 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net">matthias@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;">
An alternative approach would be to monitor the queue length (e.g. by issuing a passive queue.declare) and create/destroy workers based on that information. That way queues can still do queuing, which helps in smoothing out temporary spikes.<br>
<br>
<br>
Regards,<br><font color="#888888">
<br>
Matthias.<br>
</font></blockquote></div><br>I was trying hard (maybe a little too hard :) not to have any busy loops in my code.<br><br>Getting used to dynamic queues will take me a bit of time. It's ever so slightly too flexible. I've read about various usage scenarios in various blogs. But in general, they all tend to be a bit on the generic and vague side. Does anyone have pointers to real life writeups? I guess I should attempt to find time to write one myself, once my project is nearing completion.<br>
<br>Thanks,<br>Robby<br><br>