yeah, i think yourkit is the way to go.
Martijn Dashorst wrote: > > At my job we were able to connect yourkit to our production server and > diagnose the problem in that way. If you have such spikes, it usually > is the garbage collector trying to clean up. > > Martijn > > On Mon, Apr 27, 2009 at 10:39 PM, Douglas Ferguson > <doug...@douglasferguson.us> wrote: >> We are experiencing some hard to trace performance issues (CPU pegged by >> JAVA). so we want to implement some logging in order to Audit the code. >> >> Any suggestions on wicket state that we can easily print out? I.E. size >> of page map? Etc? >> >> D/ >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.5 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- View this message in context: http://www.nabble.com/Logging-for-performance-analysis-tp23264635p23291442.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
