qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Ross (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-4287) Poor performance when a priority queue with a ring queue policy has a large backlog
Date Fri, 13 Jun 2014 12:06:01 GMT

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

Justin Ross updated QPID-4287:
------------------------------

    Fix Version/s: 0.26

> 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
>            Assignee: Alan Conway
>             Fix For: 0.26
>
>         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 was sent by Atlassian JIRA
(v6.2#6252)

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


Mime
View raw message