f1amingo opened a new issue, #8837:
URL: https://github.com/apache/rocketmq/issues/8837

   ### Before Creating the Enhancement Request
   
   - [X] I have confirmed that this should be classified as an enhancement 
rather than a bug/feature.
   
   
   ### Summary
   
   In the current implementation, a codec thread pool is set up for Netty, 
which is used to perform tasks such as encoding/decoding, and statistics.
   
   We found that removing the codec thread pool and directly assigning these 
computational tasks to the NIO selector threads results in performance 
improvement.
   
   Since these tasks do not involve IO operations, they will not block the NIO 
selector threads.
   
   ### Motivation
   
   Our stress test results show that removing the codec thread pool can achieve 
higher TPS (5% increase) and also reduce CPU usage (4% reduction).
   #### [TPS Comparison] Before:
   ![TPS 
Before](https://github.com/user-attachments/assets/96532784-8a4e-4ea4-b34e-88a6374b6794)
   #### [TPS Comparison] After:
   ![TPS 
After](https://github.com/user-attachments/assets/d683104d-eef3-4e9d-a151-4920228a4b6d)
   
   ----
   
   #### [CPU Comparison] Before:
   
![image](https://github.com/user-attachments/assets/aefbeb4a-4dfc-4d89-80e1-bacc644f0ed3)
   #### [CPU Comparison] After:
   
![image](https://github.com/user-attachments/assets/4381185c-74f5-4519-a621-94805cfed60a)
   
   ### Describe the Solution You'd Like
   
   Remove the codec thread pool `NettyRemotingServer #defaultEventExecutorGroup`
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to