[
https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223646#comment-15223646
]
Remko Popma commented on LOG4J2-1116:
-------------------------------------
Understood.
Perhaps web apps can still benefit from Log4j using the garbage-free layout API
(using Encoder and ByteBufferDestination). I'll revisit the use of ThreadLocals
in that area and see if they can be reduced to just JDK classes.
Based on data in Mission Control from the simple logging example, 90% of memory
reclaimed by GC comes from char[] and byte[] arrays, so just the layout stuff
will have a big impact.
> Web app-friendly thread locals for gc-free logging (was: upgrade to log4j2
> causes too frequent minor gc)
> --------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1116
> URL: https://issues.apache.org/jira/browse/LOG4J2-1116
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.3
> Environment: jdk1.6
> slf4j 1.7.9
> log4j2.3
> Reporter: Mingjiang Shi
> Assignee: Ralph Goers
> Priority: Critical
> Fix For: 2.6
>
> Attachments: Log4jThreadLocal.java, Log4jThreadLocal.java
>
>
> We used slf4j+log1.2 in our spring web application. Due to the log4j1.0
> performance issue, we upgrade it to log4j2. When it goes to production, it
> experienced very frequent minor gc (once per second) even though the eden
> area is not full. For example, the eden area just occupied 10%, the minor gc
> also happens. The issue disappears when rolling back to log4j1.2.
> Can anyone show some hints on diagnose this issue? Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
