[rabbitmq-discuss] Workpool memory leak on 3.3.1?
gperes at daitangroup.com
Mon Jun 2 17:24:07 BST 2014
I just shot for 'memory leak' cause I saw it was an issue in the past. I've
been trying to improve our consumer logic to make it faster/more effective.
It was good refactoring, but it can only take us too far before we run out
of memory again.
I'll look into the QoS and manual acks. Those were good tips. Should I have
any questions, I'll post back.
Thank you very much for your time.
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Workpool-memory-leak-on-3-3-1-tp35984p35988.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
More information about the rabbitmq-discuss