RockteMQ-AI commented on issue #1340: URL: https://github.com/apache/rocketmq-clients/issues/1340#issuecomment-5364729188
**Issue Evaluation** Category: `bug` | Status: **Confirmed** This is a valid performance issue. When a `ProcessQueue` drains its cache below the per-queue threshold, the consumer still waits the full `cacheBackoffMs` before the next receive cycle, because the backoff timer is not reset upon cache drain. This introduces unnecessary latency in asymmetric queue-load scenarios. **Root Cause:** The backoff scheduling in `PushConsumerImpl` does not account for cache-drain events — the next receive is always delayed by the full backoff interval regardless of current cache utilization. **Impact:** Increased message delivery latency when queue assignments are imbalanced across consumers. **Severity:** medium A fix should reset or shorten the backoff delay when a `ProcessQueue` transitions from above-threshold to below-threshold. --- *Automated evaluation by RockteMQ-AI* -- 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]
