[LOG4J2-2391] Investigate ThrowableProxy performance

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.11.1
• Assignee: Carter Kozak
• Reporter: Carter Kozak
• Created: 23/Jul/18 18:30
• Updated: 29/Jul/20 07:32

Description

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.

Issue Links

• links to: GitHub Pull Request #210

Sub-Tasks

• AsyncLoggerContextSelector with ThrowableProxy uses incorrect CCL: Open
• Mixed async loggers should not fully initialize ThrowableProxy unless it is used: Open