You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/03/15 03:57:00 UTC
[jira] [Commented] (LOG4J2-2792) Performance issue in log4j 2.12.1
and log4j 2.13.0
[ https://issues.apache.org/jira/browse/LOG4J2-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059545#comment-17059545 ]
Ralph Goers commented on LOG4J2-2792:
-------------------------------------
Any new info on this? Even providing your configuration would provide some information.
> 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: 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)