Re: Logging for performance analysis

2009-04-28 Thread Jonathan Locke
> 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 maili

Re: Logging for performance analysis

2009-04-28 Thread Daniel Toffetti
Douglas Ferguson douglasferguson.us> writes: > > I will definitely share my findings. I saw 400% CPU (we have 4 proc box), > the other day! > > What debugging approach are you taking? > > Douglas > I've tried a couple monitoring tools for Tomcat, but they where too intrusive (required ins

Re: Logging for performance analysis

2009-04-28 Thread Martijn Dashorst
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 wrote: > We are experiencing some hard to trace per

RE: Logging for performance analysis

2009-04-27 Thread Douglas Ferguson
@wicket.apache.org Subject: Re: Logging for performance analysis Douglas Ferguson douglasferguson.us> writes: > > 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

Re: Logging for performance analysis

2009-04-27 Thread Daniel Toffetti
Douglas Ferguson douglasferguson.us> writes: > > 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

Re: Logging for performance analysis

2009-04-27 Thread Jeremy Thomerson
turn on the request logger - it dumps a ton of data on every request. i think it's in the debug settings IIRC -- Jeremy Thomerson http://www.wickettraining.com On Mon, Apr 27, 2009 at 3:39 PM, Douglas Ferguson wrote: > We are experiencing some hard to trace performance issues (CPU pegged by

Logging for performance analysis

2009-04-27 Thread Douglas Ferguson
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/ -