logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1296) Add MessageFactory that reuses a cached Message instance
Date Wed, 24 Feb 2016 00:12:18 GMT

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

Remko Popma commented on LOG4J2-1296:

My goal is to create an allocation-free execution path in Log4j with some reasonable configuration.
 If there is still some temp object allocation on each event we'd still be contributing to
GC pressure. It would be snatching defeat from the jaws of victory! :-)

> Add MessageFactory that reuses a cached Message instance
> --------------------------------------------------------
>                 Key: LOG4J2-1296
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1296
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: API
>    Affects Versions: 2.5
>            Reporter: Remko Popma
>            Assignee: Remko Popma
> As discussed in LOG4J2-1270, all current MessageFactory implementations create new temporary
Message objects. A GC-free configuration needs a different MessageFactory that reuses Message
> When Messages are being reused, async logging components need to be aware of this and
ensure the Message _content_  (rather than the Message instance itself) is passed to the background
thread. However, Messages that are not reusable should be passed to the background thread

This message was sent by Atlassian JIRA

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

View raw message