[
https://issues.apache.org/jira/browse/QPID-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7559:
-------------------------------
Summary: [Java Broker] Potentially improve performance by refactoring
QueueConsumerManager (was: [Java Broker] Potential Performance Improvements)
> [Java Broker] Potentially improve performance by refactoring
> QueueConsumerManager
> ---------------------------------------------------------------------------------
>
> Key: QPID-7559
> URL: https://issues.apache.org/jira/browse/QPID-7559
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Lorenz Quack
>
> In no particular order
> * In {{org.apache.qpid.server.queue.AbstractQueue#deliverSingleMessage}} we
> currently call {{_queueConsumerManager.setNotified()}} twice to guard against
> a race condition (a message becoming available just before a consumer is
> moved from notified to interested). We could potentially optimise this by
> merging the Notified and Interested lists.
> * Currently, when the broker receives a AMQP command the response is handled
> synchronously in the same IO thread. We could try to separate those steps
> into three distinct asynchronous tasks: receive message, process, send
> response. This could help us making more efficient use of the IO bandwidth by
> pipe-lining the IO workload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
