Ah yes, I see that. I use JProfiler but it's not free. I've also found Eclipse Memory Analyzer very useful, so you might try JVM monitor. VisualVM will also be enough, for now you're just trying to see what's getting the most CPU time since that's maxed out when things slow down.
What happens when you give the heap more memory, does it take longer to slow down? > On 14 Oct 2013, at 22:12, rjsteixeira <rica...@ctrler.eu> wrote: > > I'm not using the stateful option right now because the timer is set to run > only once (for testing reasons). > > Any recomendations for a profiler? > > I'm at home right now but I'm thinking of using VisualVM tomorrow. > > Thanks. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-gradually-slowing-down-with-large-sql-results-tp5741560p5741565.html > Sent from the Camel - Users mailing list archive at Nabble.com.
