[rabbitmq-discuss] basic.qos prefetch across multiple queues - useful?

Alvaro Videla videlalvaro at gmail.com
Mon Mar 18 18:36:10 GMT 2013


I think per-queue would be better, at least for the PHP people. Since PHP
doesn't support threads is not common to have multiple channels in one
process. So basic.qos as is today limits every queue in the channel for
most PHP scripts.

I guess other languages like Python are in the same area.



On Mon, Mar 18, 2013 at 7:30 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Is anybody setting a basic.qos prefetch limit on channels with consumers
> on multiple queues?
> If so, are you relying on the fact that the prefetch limit applies
> *across* queues rather than *per* queue?
> That feature entails considerable implementation complexity and has a
> substantial performance impact on consuming from basic.qos-limited channels
> in general. And I've just found a bug in that area of the code, fixing of
> which will make the implementation even more complex and hurt performance
> even more.
> Hence I am trying to gauge people's opinion on whether we could make the
> prefetch limit apply per-queue instead.
> Regards,
> Matthias.
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130318/1a57ba0d/attachment.htm>

More information about the rabbitmq-discuss mailing list