[jira] [Updated] (QPID-4287) Poor performance when a priority queue with a ring queue policy has a large backlog

["Jason Dillaman (JIRA)" <ji...@apache.org>]

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

Jason Dillaman updated QPID-4287:
---------------------------------

    Attachment: qpid-4287.patch

Quick POC to reduce the performance degradation in the ring queue policy.  
                
> 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