[
https://issues.apache.org/jira/browse/LOG4J2-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-324.
--------------------------------
Resolution: Fixed
Fixed in commits 842c4ad5 (memory usage reduction) and e0a77a3b.
It turns out that StatusLogger already has a system property
({{log4j2.status.entries}}) for users to determine the queue size. I made a
small change to also support for the queue to be zero size. This way StatusData
is not stored in memory.
> Potential performance improvement for StatusLogger
> --------------------------------------------------
>
> Key: LOG4J2-324
> URL: https://issues.apache.org/jira/browse/LOG4J2-324
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.0-beta8
> Reporter: Remko Popma
> Assignee: Remko Popma
> Fix For: 2.5
>
>
> From discussion on the mailing list - please feel free to edit this
> description.
> From: Ralph Goers
> To: Log4J Developers List <log4j-dev@logging.apache.org>
> Sent: Wednesday, July 24, 2013 7:57 AM
> Subject: Re: Config additions, WAS: Confused: want low latency: do I need
> BOTH async logger AND async appender??
> I think I just came up with another attribute for the JMX element. I'll have
> to look at the status logger but I believe it is always creating a StatusData
> object and putting it in a ring buffer so they can be printed later. This
> will actually create a lot of objects and will impact performance. So we will
> want to add a statusLevel attribute to the JMX element to specify what the
> level is on the events that should be added to the buffer.
> It was actually kind of cool though as the person doing the performance test
> looked at the JMX stats and even though the status was set to error in the
> configuration they had lots of debug messages in JMX that were quite helpful
> to verify a misconfiguration.
> Ralph
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
