RockteMQ-AI commented on issue #748: URL: https://github.com/apache/rocketmq-spring/issues/748#issuecomment-5192825958
**Issue Evaluation** Category: `question` In RocketMQ 5.x, the threading model was simplified. `consumeThreadMin`/`consumeThreadMax` were deprecated because the 5.x client uses a different consumption model — the `PushConsumer` now manages its own thread pool internally with a fixed thread count (`consumeThreadNumber`). **Regarding your concerns:** 1. **Thread waste with many topics:** Each consumer instance creates `consumeThreadNumber` threads. With N topics × M threads, the total is indeed N×M. Consider reducing `consumeThreadNumber` or consolidating topics. 2. **Peak throughput:** The 5.x client relies on async I/O for throughput rather than thread count scaling. If you need dynamic thread scaling, this is a valid feature request for the upstream client. 3. **Topic merging:** This is an application design concern — consider using message tags or separate consumer groups for different business logic within the same topic. --- *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]
