[
https://issues.apache.org/jira/browse/LOG4J2-2391?focusedWorklogId=422070&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-422070
]
ASF GitHub Bot logged work on LOG4J2-2391:
------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Apr/20 14:46
Start Date: 14/Apr/20 14:46
Worklog Time Spent: 10m
Work Description: carterkozak commented on issue #210: [LOG4J2-2391]
Lazily initialize ThrowableProxy data
URL: https://github.com/apache/logging-log4j2/pull/210#issuecomment-613486202
Sorry, this has gotten stale and I need to come back to the problem when I
have some time. I'm not confident this is the best solution as it only defers
initialization instead of reducing the total cost, so it's only helpful for the
AsyncLoggerConfig codepath, not AsyncLoggerContextSelector (fully async) or
synchronous modes. I'll take a look at updating the async config code to defer
throwableproxy initialization in the same way as fully async so they're more
closely comparable.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 422070)
Time Spent: 20m (was: 10m)
> 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
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
