You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2016/12/02 14:23:58 UTC
[jira] [Updated] (QPID-7566) [Java Broker] Potentially improve
performance by separating IO from processing of commands
[ https://issues.apache.org/jira/browse/QPID-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lorenz Quack updated QPID-7566:
-------------------------------
Description: 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. (was: 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.)
> [Java Broker] Potentially improve performance by separating IO from processing of commands
> ------------------------------------------------------------------------------------------
>
> Key: QPID-7566
> URL: https://issues.apache.org/jira/browse/QPID-7566
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Lorenz Quack
>
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org