logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wulf Wechsung ...@contexo.de>
Subject Performance and Logger.getLogger()
Date Wed, 02 Apr 2003 14:10:59 GMT


I read in the faq that calling Logger.getLogger() will kill app performance.
I am currently writing a wrapper for a beast called the SAP/webMethod
business connector which is an app-server providing a 'unique' flow language
to programm services. It would be to quite an effort to ask the developers
of those services to keep references to their logger and pass it for each
log statement, so I would did an implementation that determines which logger
to use by itself. Unfortunatly it has to call Logger.getLogger() for each
The question is: would application performance be better if I kept the
Logger references in a hashtable and retrieved them from there by name? 
This might seem like an unnecessary question but I just don't know how much
over-heap there is involved when calling Logger.getLogger().

Thanks in advance,

PS:"I made a serious effort to see if this has been asked before via the
mail archives, so please excuse me if it, in fact, has been"

To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org

View raw message