Is Message.format() (I guess this would be used within) better than
using a StringBuilder? Further, thinking about what potentially to log
is also a good idea.
I think if logging is a bottleneck then often the problem is not the
right library to use.
My 2 cents...
Am 23.07.2009 um 10:59 schrieb Pavel Tavoda:
> Hello,
>
> can we switch from commons-logging system to Log4J or even to standard
> Java logging? When you make many detail logging statements which are
> normally filtered in production environment system is still spending a
> lot of time preparing text messages because commons logging doesn't
> allow parametrized messages like:
> log.info("text {1} {0}.{2}", param0, param1, param2);
>
> You are forced to concat strings, what is HUGE performance bottleneck
> because strings are constructed before they are filtered. Always to
> make if(...) condition before I log something isn't good practice when
> other logging systems solving it automatically.
>
> Any ideas or thoughts in this area?
>
> Pavel
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Fornax-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fornax-developer
------------------------------------------------------------------------------
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
