[jira] [Commented] (LOG4J2-2795) Make LogManager/LoggerContext creation time reasonable

["Matt Sicker (Jira)" <ji...@apache.org>]

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

Matt Sicker commented on LOG4J2-2795:
-------------------------------------

This is tangentially related to LOG4J2-2694 and the new dependency injection system which is adapted from how CDI works which should allow for generated java code as an alternative to reflection, though use of GraalVM could also help as those reflective operations turn into metadata lookups.

> Make LogManager/LoggerContext creation time reasonable
> ------------------------------------------------------
>
>                 Key: LOG4J2-2795
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2795
>             Project: Log4j 2
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 2.13.0
>            Reporter: Romain Manni-Bucau
>            Priority: Major
>
> 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?).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)