[
https://issues.apache.org/jira/browse/LOG4J2-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180926#comment-17180926
]
Ralph Goers edited comment on LOG4J2-2909 at 8/20/20, 2:32 AM:
---------------------------------------------------------------
It would be great if [~rpopma] could take a look at this as all of the time
seems to be spent in the Disruptor. I recall that there were changes to add
different wait strategies but I'm not the expert on this.
Actually, Looking again I am noticing that while the overall time in
Logger.info went doubled the time spent in the Disruptor is about the same.
This is very odd since there are a bunch of other methods that have to be in
the call stack that aren't being shown in these pictures. Logger.info doesn't
do much itself so the time cannot be in that method.
I can understand if you don't want to share the SNAPSHOT publicly but can you
provide it privately?
was (Author: [email protected]):
It would be great if [~rpopma] could take a look at this as all of the time
seems to be spent in the Disruptor. I recall that there were changes to add
different wait strategies but I'm not the expert on this.
Actually, Looking again I am noticing that while the overall time in
Logger.info went doubled the time spent in the Disruptor is about the same.
This is very odd since there are a bunch of other methods that have to be in
the call stack that aren't being shown in these pictures. Logger.info doesn't
do much itself so the time cannot be in that method.
> Version Upgrade of log4j2 jars from 2.10.0 to 2.13.2 cause TPS degradation
> ---------------------------------------------------------------------------
>
> Key: LOG4J2-2909
> URL: https://issues.apache.org/jira/browse/LOG4J2-2909
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j-Audit
> Affects Versions: 2.13.2
> Reporter: Ali Murtaza
> Priority: Critical
> Fix For: 2.10.0
>
> Attachments: Capture.PNG, JBoss4.2.3-log4j2.10.0.PNG,
> JBoss4.2.3-log4j2.13.2.PNG, Log4jMethod.PNG, NonProblemLog4j2.10.0-part1.PNG,
> NonProblemLog4j2.10.0-part2.PNG, NonProblemLog4j2.10.0-part3.PNG,
> NonProblemLog4j2.10.0-part4.PNG, NonProblemLog4j2.10.0-part5.PNG,
> NonProblemLog4j2.10.0-part6.PNG, ProblemLog4j2.13.2-part1.PNG,
> ProblemLog4j2.13.2-part2.PNG, ProblemLog4j2.13.2-part3.PNG, log4j2
> Configuration.xml
>
>
> Hi,
> After updating the log4j2 jars from *2.10.0* to *2.13.2* in *TOMCAT 9.0.31*
> and *JBOSS 4.2.3* we are facing almost *40% TPS* degradation in our
> application.
> Further Analysis shows that almost *28%* of total time is taken by log4j2
> method.
> !Log4jMethod.PNG!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
