3424672656 opened a new issue, #8442: URL: https://github.com/apache/rocketmq/issues/8442
### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary As concurrent systems grow more complex internally in RockteMQ, deploying effective lock management strategies is key to preserving performance. Our goal is to optimize the locking mechanism and improve performance. I have written the proposal and you can see it by the link below: https://shimo.im/docs/473QM8m8ByCn6l3w/ We will implement the proposed changes by 3 phases. - [ ] 1.Optimize the locking logic for message delivery to commitLog 2.Spin optimal degree K retreat locking mechanism is introduced 3.Optimize the back pressure mechanism of the client - [ ] 1.Adaptive lock is implemented initially 2.Introduce other locking mechanisms 3.Optimize message receiving logic - [ ] 1.Improved adaptive locks 2.Provides tools for adjusting the lock mechanism 3.Design the necessary tests ### Motivation null ### Describe the Solution You'd Like null ### Describe Alternatives You've Considered null ### 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
