You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2018/10/09 19:28:00 UTC

[jira] [Created] (QPIDJMS-416) Move protocol processing work into the netty event loop thread

Timothy Bish created QPIDJMS-416:
------------------------------------

             Summary: 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
             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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org