logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16229] - Convenience methods to cut object allocations in application code
Date Thu, 10 Jun 2004 06:27:45 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=16229>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=16229

Convenience methods to cut object allocations in application code





------- Additional Comments From linus@tigris.org  2004-06-10 06:27 -------
Here is a test case for you. Notice that theGood runs several times faster 
than theBad while producing the same output.

On my computer:
1000 laps 48 times faster.
3000 laps 387 times faster.
10000 laps 8025 times faster.

In theUgly, the code that actually does something is almost completely hidden 
by the log statements.

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


Mime
View raw message