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

Ralph Goers commented on LOG4J2-2909:
-------------------------------------

I have JProfiler 11.1.4 installed on my MacBook Pro. No matter how I look at 
this snapshot I can't find anything useful in it.  The only thing I can tell is 
that you have lots of logging going on from all over your application. Is it 
possible you can get a trial of YourKit and try using that for profiling? I am 
just not seeing anything inside of Log4j other than logger.info and I know that 
method has almost zero overhead.

Scheduling a meeting is possible. What timezone are you in?  I am based in 
Arizona so I am UTC-7

> 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, 
> image-2020-08-31-14-54-27-974.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)

Reply via email to