[LOG4J2-2795] Make LogManager/LoggerContext creation time reasonable

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.13.0
• Component/s: Core
• Epic Link: Mean Bean Machine
• Assignee: Unassigned
• Reporter: Romain Manni-Bucau
• Created: 02/Mar/20 15:45
• Updated: 01/Dec/23 22:24

Description

Currently (2.13), LogManager.getLogger("xxx") takes ~600ms on a cold JVM by itself.

For a logging framework it is likely way too much (by comparison a CDI test with classpath scanning takes ~50ms).

 

This ticket is about trying to be faster (maybe by removing java serialization usage and reducing registry usage + reflection of plugins by generating java code?).

Issue Links

• is a parent of: LOG4J2-3442 Defer hostname lookup until first used
• is a parent of: LOG4J2-3441 Defer loading of StrLookup plugin classes until first use
• is a parent of: LOG4J2-3443 Defer JMX initialization unless opted in
• is a parent of: LOG4J2-3459 Reduce use of class static initialization blocks
• is a parent of: LOG4J2-3450 Add mechanism to disable Log4j2 automatic configuration
• relates to: LOG4J2-2802 Log4j-core must only require java.base