Re: Logging for performance analysis
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 > 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
Re: Logging for performance analysis
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 installation on the server). There was one in particular that only required configuring Java for JMX (Management Extensions) but I had to do other things and I will get into it in a few days I hope. My suspicion is that the problem can be memory leaks in the library we use to access the database. It was withdrawn from sourceforge recently and I plan to change it to something else. For your interest, I can tell you that the response and performance greatly improved when I changed the model for a couple of data tables to LoadableDetachableModel. This is our first Java web app so a lot of inexperience with all the tools, but Tomcat not only get stuck to 30-80% CPU from time to time but it even crashes sometimes, I'm afraid I'm missing some obvious configuration. Cheers, Daniel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Logging for performance analysis
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 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
RE: Logging for performance analysis
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 -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Daniel Toffetti Sent: Monday, April 27, 2009 9:46 PM To: users@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 state that we can easily print out? I.E. size of page map? Etc? > > D/ Hi, I'm having similar problems, my setup is: Java 1.6.10, Wicket 1.3.5 and Tomcat 6 on Windows XP. Tomcat seems to need 50% CPU from time to time, and often for a very long time. Will try Jeremy's suggestion, mind to share your findings ? Cheers, Daniel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
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 state that we can easily print out? I.E. size of page map? Etc? > > D/ Hi, I'm having similar problems, my setup is: Java 1.6.10, Wicket 1.3.5 and Tomcat 6 on Windows XP. Tomcat seems to need 50% CPU from time to time, and often for a very long time. Will try Jeremy's suggestion, mind to share your findings ? Cheers, Daniel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Logging for performance analysis
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 > 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 > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Logging for performance analysis
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
