qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-4287) Poor performance when a priority queue with a ring queue policy has a large backlog
Date Mon, 01 Oct 2012 21:05:08 GMT

     [ https://issues.apache.org/jira/browse/QPID-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alan Conway resolved QPID-4287.
-------------------------------

    Resolution: Not A Problem

This fix is not relevant on the current trunk, it already has a similar change.
                
> Poor performance when a priority queue with a ring queue policy has a large backlog
> -----------------------------------------------------------------------------------
>
>                 Key: QPID-4287
>                 URL: https://issues.apache.org/jira/browse/QPID-4287
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.18
>            Reporter: Jason Dillaman
>         Attachments: qpid-4287.patch
>
>
> The ring queue policy utilizes a single deque to store messages in priority and FIFO
order.  When inserting messages of mixed priority into a queue with a large (>100,000)
message backlog, the performance degrades quickly enough to potentially block all broker worker
threads if they all are publishing to the same queue.  Recommend separating the ring queue
data structure into separate deques based upon message priority in order to avoid the potential
for reshuffling the deque with each incoming message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message