You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Douglas Ferguson <do...@douglasferguson.us> on 2009/04/27 22:39:55 UTC

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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Logging for performance analysis

Posted by Jeremy Thomerson <je...@wickettraining.com>.
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
<do...@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Logging for performance analysis

Posted by Jonathan Locke <jo...@gmail.com>.

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
> <do...@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Logging for performance analysis

Posted by Martijn Dashorst <ma...@gmail.com>.
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
<do...@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Logging for performance analysis

Posted by Daniel Toffetti <dt...@yahoo.com.ar>.
Douglas Ferguson <douglas <at> 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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: https://issues.apache.org/jira/browse/WICKET-847

Posted by Johan Compagner <jc...@gmail.com>.
no that one isnt in 1.3.5

The commit is done by igor together with:

WICKET-1916, WICKET-1998

On Tue, Apr 28, 2009 at 09:43, Steve Swinsburg
<s....@lancaster.ac.uk>wrote:

> Comparing the commits attached to the Jira to what is in the 1.3.5 tag in
> svn shows it's not.
>
> I'm a little confused by that, does the committers not fix in trunk, merge
> back to the appropriate branches (1.3.x) then cut tags from the branches
> (1.3.5, 1.3.6)?
>
> Steve
>
>
> On 28/04/2009, at 8:36 AM, Martijn Dashorst wrote:
>
>  The commit was before 1.3.5 was cut, so IMO it should be already in 1.3.5.
>>
>> Martijn
>>
>> On Tue, Apr 28, 2009 at 9:31 AM, Jeremy Thomerson
>> <je...@wickettraining.com> wrote:
>>
>>> There's a comment that says that it's actually NOT in 1.3.5 - implying
>>> that the fix version is incorrect.  But Igor's comment seems to
>>> indicate that it WAS fixed.
>>>
>>> I don't know which is true, but whoever really wants to know should
>>> just try it and see - and then comment on the jira to make it clear.
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>>
>>>
>>>
>>> On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg
>>> <s....@lancaster.ac.uk> wrote:
>>>
>>>> The fix version for that issue says 1.3.5 so unless people use Jira
>>>> incorrectly, it's in 1.3.5. Likewise for the previous issue that people
>>>> want
>>>> to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so
>>>> should be
>>>> in 1.3.6 already.
>>>>
>>>>
>>>> --Steve
>>>>
>>>> On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
>>>>
>>>>  So, is this fixed in 1.3.6?
>>>>>
>>>>> https://issues.apache.org/jira/browse/WICKET-847
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>

Re: https://issues.apache.org/jira/browse/WICKET-847

Posted by Steve Swinsburg <s....@lancaster.ac.uk>.
Comparing the commits attached to the Jira to what is in the 1.3.5 tag  
in svn shows it's not.

I'm a little confused by that, does the committers not fix in trunk,  
merge back to the appropriate branches (1.3.x) then cut tags from the  
branches (1.3.5, 1.3.6)?

Steve

On 28/04/2009, at 8:36 AM, Martijn Dashorst wrote:

> The commit was before 1.3.5 was cut, so IMO it should be already in  
> 1.3.5.
>
> Martijn
>
> On Tue, Apr 28, 2009 at 9:31 AM, Jeremy Thomerson
> <je...@wickettraining.com> wrote:
>> There's a comment that says that it's actually NOT in 1.3.5 -  
>> implying
>> that the fix version is incorrect.  But Igor's comment seems to
>> indicate that it WAS fixed.
>>
>> I don't know which is true, but whoever really wants to know should
>> just try it and see - and then comment on the jira to make it clear.
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>>
>>
>> On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg
>> <s....@lancaster.ac.uk> wrote:
>>> The fix version for that issue says 1.3.5 so unless people use Jira
>>> incorrectly, it's in 1.3.5. Likewise for the previous issue that  
>>> people want
>>> to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so  
>>> should be
>>> in 1.3.6 already.
>>>
>>>
>>> --Steve
>>>
>>> On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
>>>
>>>> So, is this fixed in 1.3.6?
>>>>
>>>> https://issues.apache.org/jira/browse/WICKET-847
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>

Re: https://issues.apache.org/jira/browse/WICKET-847

Posted by Martijn Dashorst <ma...@gmail.com>.
The commit was before 1.3.5 was cut, so IMO it should be already in 1.3.5.

Martijn

On Tue, Apr 28, 2009 at 9:31 AM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> There's a comment that says that it's actually NOT in 1.3.5 - implying
> that the fix version is incorrect.  But Igor's comment seems to
> indicate that it WAS fixed.
>
> I don't know which is true, but whoever really wants to know should
> just try it and see - and then comment on the jira to make it clear.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg
> <s....@lancaster.ac.uk> wrote:
>> The fix version for that issue says 1.3.5 so unless people use Jira
>> incorrectly, it's in 1.3.5. Likewise for the previous issue that people want
>> to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so should be
>> in 1.3.6 already.
>>
>>
>> --Steve
>>
>> On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
>>
>>> So, is this fixed in 1.3.6?
>>>
>>> https://issues.apache.org/jira/browse/WICKET-847
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: https://issues.apache.org/jira/browse/WICKET-847

Posted by Jeremy Thomerson <je...@wickettraining.com>.
There's a comment that says that it's actually NOT in 1.3.5 - implying
that the fix version is incorrect.  But Igor's comment seems to
indicate that it WAS fixed.

I don't know which is true, but whoever really wants to know should
just try it and see - and then comment on the jira to make it clear.

--
Jeremy Thomerson
http://www.wickettraining.com




On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg
<s....@lancaster.ac.uk> wrote:
> The fix version for that issue says 1.3.5 so unless people use Jira
> incorrectly, it's in 1.3.5. Likewise for the previous issue that people want
> to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so should be
> in 1.3.6 already.
>
>
> --Steve
>
> On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
>
>> So, is this fixed in 1.3.6?
>>
>> https://issues.apache.org/jira/browse/WICKET-847
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: https://issues.apache.org/jira/browse/WICKET-847

Posted by Steve Swinsburg <s....@lancaster.ac.uk>.
The fix version for that issue says 1.3.5 so unless people use Jira  
incorrectly, it's in 1.3.5. Likewise for the previous issue that  
people want to hold up the 1.3.6 release for, it has a fix version of  
1.3.6 so should be in 1.3.6 already.


--Steve

On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:

> So, is this fixed in 1.3.6?
>
> https://issues.apache.org/jira/browse/WICKET-847
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>

https://issues.apache.org/jira/browse/WICKET-847

Posted by Douglas Ferguson <do...@douglasferguson.us>.
So, is this fixed in 1.3.6?

https://issues.apache.org/jira/browse/WICKET-847

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

RE: Logging for performance analysis

Posted by Douglas Ferguson <do...@douglasferguson.us>.
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:news@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 <douglas <at> 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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Logging for performance analysis

Posted by Daniel Toffetti <dt...@yahoo.com.ar>.
Douglas Ferguson <douglas <at> 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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org