[
https://issues.apache.org/jira/browse/QPIDJMS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435520#comment-17435520
]
ASF GitHub Bot commented on QPIDJMS-553:
----------------------------------------
tabish121 commented on pull request #45:
URL: https://github.com/apache/qpid-jms/pull/45#issuecomment-953985565
> @gemmellr
>
> Right now I'm not enforcing that a pooled (shared) event loop group
matches the configured transport event loop type that is borrowing it, meaning
that Netty woudl fail on transport connect because of channel/event loop
mismatch, but I suppose this is not a valid use case
I'm not particularly fond of one configuration option being able to cause
breakage should another connection in the same VM have chosen not to use the
same native (or not) transport type. It might seem benign now but guess whose
going to have to support the case when it comes up later.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Shared Netty event loop group
> -----------------------------
>
> Key: QPIDJMS-553
> URL: https://issues.apache.org/jira/browse/QPIDJMS-553
> Project: Qpid JMS
> Issue Type: New Feature
> Reporter: Francesco Nigro
> Priority: Major
>
> One of the most interesting feature of Netty while using KQueue/NIO/Epoll in
> non-blocking mode is to be able to handle many connections with few threads;
> this is going to be critical and even more important with the upcoming
> IO_URING support, where the time spent on the Netty event loop to handle
> network syscalls will be further reduced, allowing syscall batching across
> different connections.
> Having the chance to handle many client connections with few Netty threads is
> already beneficial in constrained environments (containers with few cores) in
> order to reduce the native and heap memory usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
