Logger performance

[Kenneth P. Turvey]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was looking at the Logger classes the other day and I read some claims
about the performance of the Logger that I found a bit hard to believe.

Ideally what one would like is a system like the assertion system where
logging code is only executed when it is above the level being filtered
by the logging system so code like this:

thisLogger.finest("My info: " + SomeObject.performComplexCalculation());

would not execute except when the user was requesting logging at the
finest level.

I don't believe the Logger is handled this way. It would require
compiler support that I don't believe exists, wouldn't it?

Am I correct in understanding that logging should not be used in inner
loops, even for debugging (if it will be in the code in production)?

Thanks.

- --
Kenneth P. Turvey <[email protected]>
http://kt.squeakydolphin.com (not much there yet)
Jabber IM: (e-mail address removed)
Phone: (314) 255-2199

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDLeDq3naBnF2rJNURAtyZAKDFGo4CopQkwj3l+UWjXSAd/9e4tACfWX6J
5MomPDKF+vrHRTPQku8Lpuo=
=SMUy
-----END PGP SIGNATURE-----

 

[iamfractal]

Kenneth P. Turvey skrev:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was looking at the Logger classes the other day and I read some claims
about the performance of the Logger that I found a bit hard to believe.

-----END PGP SIGNATURE-----

To add to the excellent answer already received, see:
http://www.javaalmanac.com/egs/java.util.logging/Minimize.html?l=rel

I fear your fears are justified.

..ed

 

[Kenneth P. Turvey]

To add to the excellent answer already received, see:
http://www.javaalmanac.com/egs/java.util.logging/Minimize.html?l=rel

I fear your fears are justified.

That's too bad. Having all this code for logging really clutters the
code. There must be a better way.

 

[Chris Uppal]

That's too bad. Having all this code for logging really clutters the
code. There must be a better way.

AspectJ ?

-- chris

 

[Scott Ellsworth]

That's too bad. Having all this code for logging really clutters the
code. There must be a better way.

I have never found

if (logger.isLoggable(Level.FINEST)) {
logger.finest("count: "+count);
}

to be all that bad, but then I tend to have some very distinct patterns
in my logging code. For example, I log entry and exit at the top and
bottoms of methods, so I tend not to see those lines.

I suspect aspects are really the only way to get this to be clean, or
log/nolog versions of the code generated from some template or Aspect
system.

Scott

 

[_weijiang_]

Try SuperLogging from http://www.acelet.com/super/SuperLogging
You can dynamicall filter our unwanted messages: set log level,
register class... It is free.

Make your code simple. Any bug in log area is very difficult to debug:
you do not have all the condition to test it.