[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759580#comment-16759580 ]
ASF subversion and git services commented on LOG4J2-2391: --------------------------------------------------------- Commit 96e8e1ec7be4d13ca7a8aaa61a7485ae0abe1798 in logging-log4j2's branch refs/heads/master from Carter Kozak [ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=96e8e1e ] LOG4J2-2391 release note grammar s/more faster/faster > Investigate ThrowableProxy performance > -------------------------------------- > > Key: LOG4J2-2391 > URL: https://issues.apache.org/jira/browse/LOG4J2-2391 > Project: Log4j 2 > Issue Type: Task > Affects Versions: 2.11.1 > Reporter: Carter Kozak > Assignee: Carter Kozak > Priority: Major > > I've noticed when applications get into a state where they log more > exceptions than usual (e.g. network connectivity issues) thread dumps contain > many threads working inside of ThrowableProxy, loading classes. > A simple jmh benchmark of a pattern layout writing to disk with a message and > throwable appears to write about 160,000 events/second using a throwable, and > 2,000 events/second using ThrowableProxy. > I will investigate to understand where the substantial difference is coming > from, and clean up the benchmarks to add to the log4j2 benchmarking module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)