[
https://issues.apache.org/jira/browse/QPIDJMS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPIDJMS-553:
-----------------------------------
Description:
Having the chance to handle many client connections with few Netty threads can
be beneficial, eg in terms of the thread staying warm, or batching syscalls
across connections when using the coming io_uring support, plus it can already
aid in constrained environments with many connections by helping reduce the
native and heap memory usage through consolidating various data structure uses
etc.
Add a _"transport.sharedEventLoopThreads"_ URI option that can be used to
specify a number of threads to use in an EventLoopGroup shared amongst
connections active at the same time and using the same value. Default to -1
giving the existing behaviour of each connection using its own.
was:
Having the chance to handle many client connections with few Netty threads can
be beneficial, eg in terms of the thread staying warm, batching batching
syscalls across connections when using the coming io_uring support, plus it can
already aid in constrained environments with many connections by helping reduce
the native and heap memory usage through consolidating various data structure
uses etc.
Add a _"transport.sharedEventLoopThreads"_ URI option that can be used to
specify a number of threads to use in an EventLoopGroup shared amongst
connections using the same value. Default to -1 giving the existing behaviour
of each connection using its own.
> add option to use shared Netty event loop group
> -----------------------------------------------
>
> Key: QPIDJMS-553
> URL: https://issues.apache.org/jira/browse/QPIDJMS-553
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Reporter: Francesco Nigro
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 1.6.0
>
>
> Having the chance to handle many client connections with few Netty threads
> can be beneficial, eg in terms of the thread staying warm, or batching
> syscalls across connections when using the coming io_uring support, plus it
> can already aid in constrained environments with many connections by helping
> reduce the native and heap memory usage through consolidating various data
> structure uses etc.
> Add a _"transport.sharedEventLoopThreads"_ URI option that can be used to
> specify a number of threads to use in an EventLoopGroup shared amongst
> connections active at the same time and using the same value. Default to -1
> giving the existing behaviour of each connection using its own.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
