You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Payne Xu (JIRA)" <ji...@apache.org> on 2018/11/01 06:11:00 UTC
[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy
performance
[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671154#comment-16671154 ]
Payne Xu commented on LOG4J2-2391:
----------------------------------
[~ckozak] Thanks for your temporary solution, I'm looking forward the idealĀ solutionĀ :D
> 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)