Curt Arnold wrote:
On Dec 1, 2005, at 7:51 PM, Trenton D. Adams wrote:
Hi guys,
So, what's up with people writing articles about it's performance
problems?
The key metric people are interested in is performance with logging
disabled (or substantially disabled). I'm willing to take a
performance hit when I'm trying to diagnose a problem, but when
performance is critical, I'd like the performance to approach that of
code that had no logging code in it at all.
Your test appears to compare the cost of a getLogger() call with
formatting and appending a message and in that scenario, getLogger() is
relatively cheap at 5% of the total time. However, if you disable
logging and you are comparing the cost of getLogger() with
Logger.isEnabledFor(), then getLogger() would likely take up the
majority of the time, maybe in the high 90's%.
So, are you saying realtime applications should be careful then?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
