metaphor opened a new issue, #7499: URL: https://github.com/apache/rocketmq/issues/7499
### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary 1. a new instance of NettyRemotingClient is created whenever a Consumer started. 2. NettyRemotingClient use NettyClientConfig.clientCallbackExecutorThreads (which is Runtime.getRuntime().availableProcessors() by default) to init the underlying thread pools. 3. if there is 20 consumers/topics and 8 cores, the application will create 160 threads. most of them are in waiting state. this causes performance issues (slow startup) and waste of resources( a lot of waiting threads). ### Motivation predicable resources will make the application stable and resources aware in clould native environment. ### Describe the Solution You'd Like better to share one underlying netty event loop instead creating new one each time. ### Describe Alternatives You've Considered No ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
