You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by GitBox <gi...@apache.org> on 2021/10/26 15:25:06 UTC

[GitHub] [qpid-jms] franz1981 commented on pull request #44: QPIDJMS-552 JMS 2 Completion threads shouldn't scale with the number of sessions

franz1981 commented on pull request #44:
URL: https://github.com/apache/qpid-jms/pull/44#issuecomment-952051837


   There're still something to be considered while using this processing model in case JMS Sessions are used on different threads AND share the same connection:
   
   - on `main` the Netty thread handling the shared connection issue completion events vs exclusive single threaded thread pools
   - on this PR the Netty thread handling the shared connection issue completion events vs a shared thread pool
   
   If the completions event processing is heavy weight, issuing completion events vs a shared thread pool shouldn't be the bottleneck, but each completion thread processing, while if completion event processing is light-weight, reusing the same completion thread(s), kept busy as much as possible, reduce the amount of context switches and native resources used.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org