qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <robbie.gemm...@gmail.com>
Subject Re: Is there a overhead to priority queues?
Date Tue, 29 Nov 2011 19:47:16 GMT
I dont think the performance difference has ever been quantified, but
it will ultimately depend on exactly what you are doing. For example,
for persistent messaging it probably makes little difference to
performance due to the critical path being the storage, but for purely
transient messaging its likely to introduce some degredation. In terms
of memory use the priority queue contains multiple list structures in
its implementation instead of just one, but those are pretty tiny so I
dont expect youd really notice even with the extreme number of queues
that have been mentioned previously. There is no difference on the
client side really.


On 28 November 2011 23:19, Vijay Devadhar <vdevadhar@salesforce.com> wrote:
> Hi Qpid users,
> We have a use case where an application has multiple message types and only some of
> them use priority; Instead of keeping FIFO queues and PRIORITY queues separate in the
> transport layer and managing their allocation correctly in the app specific routing layer,
> I was wondering if I should create all queues in QPID as priority queues and then leave
> up to the producers to specify priority or not. This way application does not have to
> message type to FIFO vs PRIORITY requirements;
> This brings up the question as to what is the overhead on java broker and java client
side for Priority
> queues vs FIFO queues. Any experience around this?
> Thanks
> Vijay

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org

View raw message