logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Grossman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-898) Format messages asynchronously
Date Tue, 18 Nov 2014 14:22:34 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216228#comment-14216228
] 

Steven Grossman commented on LOG4J2-898:
----------------------------------------

I'm working on a low latency trading system, so we are already running around with scissors!

We'd like to be able to turn on debug logging on occasion with minimal (and predictable) impact
to the system.

A rough comparison on my notebook shows that where a particular printf call using the async
appender in 2.0.1 costs a consistent 2 micros, it costs 10 or 20 micros in 2.1 depending on
how the format string is expressed.

> Format messages asynchronously
> ------------------------------
>
>                 Key: LOG4J2-898
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-898
>             Project: Log4j 2
>          Issue Type: Improvement
>    Affects Versions: 2.0.2, 2.1
>            Reporter: Steven Grossman
>
> Formatting a message can be an expensive operation (e.g. String.format) and it is undesirable
for it to be done in the calling thread when using an async logger or appender.
> LOG4J2-763 moved this work to the calling thread.  Would you consider bringing back the
previous behavior via a config/system property?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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