|
|
|
Re: Configuring the equinox LogService [message #68180 is a reply to message #68169] |
Fri, 26 May 2006 14:16 |
Eclipse User |
|
|
|
Originally posted by: simon.kaegi.cognos.com
Hi Cameron,
There's definitely still a cost to all this.
e.g. the residual cost of creating the message and running through all the
logic in the logservice.
I've been working with an SLF4J facade to get around this. (e.g it gives an
isDebug() check and a potentially cheaper debug(...))
I've opened a related bug report but I'm wondering if this is a topic for
broader discussion?
I'm running into these low-level logging issues frequently and it would be a
good thing to set an approach.
-Simon
p.s. I don't think you can set the default threshold by System Property /
config.ini (just Config Admin) but that still seems like a good idea to me.
Opening an enhancement request...
"Cameron Ross" <cross@symboticware.com> wrote in message
news:c8cf37f1a9ae5d1840490f90177fbc74$1@www.eclipse.org...
> Thanks Tom... precisely what I was looking for.
> So, if I set log.threshold to 3 (i.e. LOG_INFO and above) and I have a
> statement like this somewhere in my bundle:
> logService.log(LogService.LOG_DEBUG, "some message"), it seems clear that
> LogService will disregard the log request. However, what is the residual
> runtime cost of this request?
>
> Cheers,
> Cameron.
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.02706 seconds