redlsz opened a new issue, #10034: URL: https://github.com/apache/rocketmq/issues/10034
### 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, if there is a backlog of messages after popRequest done, PopMessageProcessor will try to wake up waiting PopRequests to optimize consumption delay. But in scenarios where immediate message retrieval is highly unlikely, such wake-ups may result in a large amount of unnecessary polling. eg: 1. Pop queue operations are being throttled due to too many in-flight messages. 2. Pop queue operations experience heavy lock contention. ### Motivation We observed that the number of PopRequests processed per second exceeded 30w. <img width="1846" height="658" alt="Image" src="https://github.com/user-attachments/assets/4a4e8e05-19bc-4255-a069-f94ebb123a21"; /> ### Describe the Solution You'd Like In scenarios where immediate message retrieval is highly unlikely, avoid waking up PopRequests. ### Describe Alternatives You've Considered / ### 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]
