[
https://issues.apache.org/jira/browse/LOG4J2-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085952#comment-17085952
]
Ralph Goers commented on LOG4J2-2792:
-------------------------------------
You may also configure your Loggers with includeLocation="false". This will
prevent the optimization from occurring and the location information will only
be obtained when it is retrieved from the log event as it was in the past. It
would be very helpful to know it that improves things for you.
> Performance issue in log4j 2.12.1 and log4j 2.13.0
> --------------------------------------------------
>
> Key: LOG4J2-2792
> URL: https://issues.apache.org/jira/browse/LOG4J2-2792
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Core
> Affects Versions: 2.12.1, 2.13.0
> Environment: System configuration: Redhat Linux 7,12-core,16Gb RAM
> Application server: Apache tomcat 9.0.16
> Reporter: Riya Reji
> Priority: Blocker
> Attachments: 24-jstack-2020-02-23-173500.zip, log4j2.xml,
> log4j_2_13_CPU_SPIKE.PNG
>
>
> Hi,
> When log4j2 was upgraded from 2.11.0 to 2.12.1 or 2.13.0,the cpu utilization
> was spiking to 100 %. When 2.11.0 version was used the CPU utilization was
> below 40%.
>
> PFA image of CPU utilization when 2.13.0 was used
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
