[
https://issues.apache.org/jira/browse/QPIDJMS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500146#comment-17500146
]
ASF GitHub Bot commented on QPIDJMS-553:
----------------------------------------
franz1981 edited a comment on pull request #45:
URL: https://github.com/apache/qpid-jms/pull/45#issuecomment-1056916847
> The same 'this seems overly complex' comment would seem to apply around
the pooling of the group, which seems like a large amount of complex handling
for what is essentially a very simple 'Is there currently another connection
not yet fully closed down' check.
Yep, impl-wise it could be implemented with a single shared (and
synchronized) pool, but API-wise things shouldn't change, unless a shared Pool
API would handle releasing resources (but that means that the Pool should check
if a just released resource belong to it, while the `Ref::close` approach save
this check).
--
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.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
