Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
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.