[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy performance

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on LOG4J2-2391:
---------------------------------------------------------

Commit de6593f5f3b5acbb2cdb4ee91e4e1f472db5dcbb in logging-log4j2's branch refs/heads/master from [~ckozak]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=de6593f ]

[LOG4J2-2391] Refactor as much logic as possible out of ThrowableProxy

This change isolates initialization logic into a new
ThrowableProxyHelper class, and rendering logic
into ThrowableProxyRenderer.

Both new utility classes are package private. ThrowableProxy public
API has not changed.


> 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)