Sounds good. A profiler (as opposed to a sampler) should be able to tell you how many times a given method is called, so if you see that that's 1, then you'd be able to make the claim that a single call to updateIndex() is taking 3.5 minutes. But looking only at thread dumps, all you can say is that you're calling updateIndex() again 3.5 minutes later, but not 1) whether it's the same call as the first one, and 2) whether you've spent a substantial amount of the intervening time calling updateIndex() (either once or many times, whichever) or whether you actually spent most of your time doing something else but just happened to take thread dumps at times when you were calling updateIndex().
BTW, I suspect that you're right that calls to updateIndex() are where you're spending your time, but that it's many repeated calls rather than one single 3.5-minute call and rather than just happening to hit updateIndex() twice when you ran your thread dumps. But without something to prove how many calls were made and how long was spent on them, you really can't make any claims about what's happening. Tim On Mon, Apr 11, 2016 at 6:44 AM, Shobhana <shobh...@quickride.in> wrote: > I looked at only the thread dumps. I will profile with some profiler first > and see where is the broker spending more time. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-with-KahaDB-as-persistent-store-becomes-very-slow-almost-unresponsive-after-creating-large-s-tp4709985p4710583.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
