xiaobing395845388 commented on issue #5417: URL: https://github.com/apache/rocketmq/issues/5417#issuecomment-1296436873
> > > Hi @xiaobing395845388 , IMO, you mean unbounded `LinkedBlockingQueue`, and `consumeThreadMax` is too small resulting in OOM. My suggestion is to increase the value of `consumeThreadMax` to speed up message processing and decrease the value of `pullThresholdForQueue` to reduce the number of messages cached by the client. > > @xiaobing395845388 Indeed, LinkedBlockingQueue is suitable for situations where producing messages and consuming messages are about the same, and when you produce messages significantly faster than you consume them, it naturally leads to oom In this case, consumeThreadMax does no work if use LinkedBlockingQueue , consumeThreadMIn is the corePoolSize in the api of "ThreadPoolExecutor" you say"producing messages and consuming messages are about the same", we cannot controll this in product env -- 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]
