I suggest getting a copy of YourKit and profiling the application.
Unfortunately, with the behavior you are seeing this might slow the
application just enough to cause the problem to go away. However,
from
your description of the problem it sounds like you have some sort of
contention going
Jean-Philippe Daigle schrieb:
Replacing it with just this assignment (to a public var so it's not
optimized away):
_dbg_str = String.format(appack id=%s res=%s, id, ack_r);
Gives me the fast throughput case.
I wasn't too surprised to hear that your custom Log implementation was
causing
Jean-Philippe Daigle wrote:
[snip]
Ah, so there's one more thing I hadn't tried, which I just did, and
explained a bit of the situation: completely removing the
logging block
(don't check isDebugEnabled(), don't call .debug(), etc.
Removing the whole logging block results in getting the
Jörg Schaible schrieb:
Jean-Philippe Daigle wrote:
[snip]
Ah, so there's one more thing I hadn't tried, which I just did, and
explained a bit of the situation: completely removing the
logging block
(don't check isDebugEnabled(), don't call .debug(), etc.
Removing the whole logging block
[EMAIL PROTECTED] wrote:
Jörg Schaible schrieb:
Jean-Philippe Daigle wrote:
[snip]
Ah, so there's one more thing I hadn't tried, which I just did, and
explained a bit of the situation: completely removing the
logging block
(don't check isDebugEnabled(), don't call .debug(), etc.
Removing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Philippe,
Jean-Philippe Daigle wrote:
| Yes, it *should* be equivalent, but I've also tried defining a Dummy
| class, getting a static instance of it, and calling a dummy method (that
| won't get optimized away) and it's fast (~8 WU/s).
Jean-Philippe Daigle wrote:
Hi, I'm seeing some very strange performance issues around the use of
commons logging, and I'm pretty much out of ideas at this point. (Long)
explanation follows...
snip
I suggest getting a copy of YourKit and profiling the application.
Unfortunately, with
On Wed, 2008-06-25 at 17:11 -0400, Jean-Philippe Daigle wrote:
Hi, I'm seeing some very strange performance issues around the use of
commons logging, and I'm pretty much out of ideas at this point. (Long)
explanation follows...
First, two code samples (they're from a messaging system, the
Could this be related to the JRE used ?
Emmanuel Bourg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-Original Message-
From: simon [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2008 5:34 PM
To: Commons Users List
Subject: Re: Strange performance issues seen with Log.isDebugEnabled()
On Wed, 2008-06-25 at 17:11 -0400, Jean-Philippe Daigle wrote:
[snip]
Wow. Really
-Original Message-
From: Emmanuel Bourg [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2008 5:57 PM
To: Commons Users List
Subject: Re: Strange performance issues seen with Log.isDebugEnabled()
Could this be related to the JRE used ?
Emmanuel Bourg
Thanks
-Original Message-
From: Jean-Philippe Daigle
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2008 6:06 PM
To: Commons Users List
Subject: RE: Strange performance issues seen with Log.isDebugEnabled()
-Original Message-
From: simon [mailto:[EMAIL PROTECTED
On 26/06/2008, Jean-Philippe Daigle
[EMAIL PROTECTED] wrote:
-Original Message-
From: Jean-Philippe Daigle
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2008 6:06 PM
To: Commons Users List
Subject: RE: Strange performance issues seen with Log.isDebugEnabled
with Log.isDebugEnabled()
-Original Message-
From: simon [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2008 5:34 PM
To: Commons Users List
Subject: Re: Strange performance issues seen with
Log.isDebugEnabled()
On Wed, 2008-06-25 at 17:11 -0400, Jean
14 matches
Mail list logo
