Thing definitely seem to crawl dramatically when this kicks in. It basically spends 5-10 minutes doing nothing but printing messages saying it’s removing in inactive queue.
So either a mutex or a controlling thread is waiting for the inactive queues to be removed. It turns out it’s < 50k.. still high but not insane. The plan is to scale this out. So each box would handle about 50k queues. I have a work around. The reason it has so many that need to be GCd is that one of our daemons keeps a consumer on them and never releases it even if the queue is empty. So if I just release it the queues will be inactive and then get GCd more often. On Thu, Jan 29, 2015 at 4:10 PM, artnaseef <[email protected]> wrote: > I'm not sure about a mutex in this case, although there are many inside the > code, but I would say that 400k-500k queues is an insane number. > > Is it possible to re-architect the solution to bring that number down? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Performance-falls-dramatically-when-GCing-large-numbers-of-inactive-queues-tp4690685p4690691.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
