[
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 instances.
> 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 unchanged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
