[ 
https://issues.apache.org/jira/browse/QPID-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984597#comment-16984597
 ] 

Alex Rudyy commented on QPID-8385:
----------------------------------

Attached patch  
[^0001-QPID-8385-Broker-J-Delete-queue-entry-asynchronously.patch]  with 
implementation of  a second approach described above 

> [Broker-J] Improve performance of operation to dequeue queue entries on 
> message expiration or triggering ring policy
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8385
>                 URL: https://issues.apache.org/jira/browse/QPID-8385
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Broker-J
>            Reporter: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.6
>
>         Attachments: 
> 0001-QPID-8385-Broker-J-Delete-queue-entry-asynchronously.patch, 
> 0001-QPID-8385-Broker-J-Utilize-AsyncAutoCommitTransactio.patch
>
>
> AutoCommitTransaction is used to dequeue  entries on message expiration or 
> breaching ring policy threshold. As result, the dequeueing operation for 
> persistent queue entry blocks until queue entry record is removed from the 
> store and  the underlying store transaction is synced to disk. The sequential 
> removal of multiple entries can results in unnecessary delays due to  syncing 
> disk on every dequeue.
> The  broker performance for the corner cases described above can be 
> significantly improved by using  asynchronous  transactions in dequeue 
> operations.
> Asynchronous transaction does not wait for the store dequeue  transaction to 
> sync to disk. As result, the performance of removal unneeded queue entries 
> can increase.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to