[
https://issues.apache.org/jira/browse/QPIDJMS-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644067#comment-16644067
]
Timothy Bish commented on QPIDJMS-416:
--------------------------------------
Commit with change at:
[https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;a=commit;h=4314482de1e8cb7e58d8331ca0e459f32d78ab4e]
{noformat}
commit 4314482de1e8cb7e58d8331ca0e459f32d78ab4e
tree 079f592511e1de668db615db5d6eb83ec79d4a07
parent 4b8739b756fd94d77965df17c7aed84c56b95dea{noformat}
> Move protocol processing work into the netty event loop thread
> --------------------------------------------------------------
>
> Key: QPIDJMS-416
> URL: https://issues.apache.org/jira/browse/QPIDJMS-416
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.37.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Major
> Fix For: 0.38.0
>
>
> Currently the protocol specific processing is handled in its own single
> threaded executor which creates a performance drop as reads and writes are
> queued into Netty for handling. We can achieve a significant performance
> boost by handling all the protocol work inside the Netty event loop and not
> hopping between threads as we do now.
> This requires some refactoring of connect and shutdown logic and some
> safeguards around all callbacks in the transport to ensure that we always
> operate on the event loop and not one on a client thread.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
