[rabbitmq-discuss] Performance of many binding keys on a single queue

[Jerry Kuch]

Hi, Jonathan:

The routing work for an exchange is actually performed by the Erlang
process associated with the channel you're publishing on, rather than being
an independent entity as the processes that back queues are.

On a per message basis, the amount of routing work will depend on the
exchange type and whatever matching behavior is implemented for it.
 Documentation to set your expectations for the different exchange types
can be found around the RabbitMQ website, e.g. here, where the performance
improvements to topic exchanges were first written up:

http://www.rabbitmq.com/blog/tag/trie/

...as well as in the Manning book "RabbitMQ in Action" IIRC.

Best regards,
Jerry

On Fri, Feb 15, 2013 at 12:56 PM, Jonathan <jhalterman at gmail.com> wrote:

> I'm curious about the impact of having many (hundreds or thousands) of
> binding keys on a single queue. Can I expect messages to still be routed to
> the queue in more or less constant time? Does it depend on the exchange
> type (topic versus direct)? I was thinking that routing in a direct
> exchange at least might be constant time since no wildcard matching is
> needed and might involve a simple hash lookup.
>
> Thanks,
> Jonathan
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> 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/20130215/a44f7114/attachment.htm>