[
https://issues.apache.org/jira/browse/LOG4J2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515116#comment-17515116
]
Romain Manni-Bucau commented on LOG4J2-2795:
--------------------------------------------
[~mattsicker] AFAIK it is not the case on master since
org.apache.logging.log4j.plugins.util.PluginManager#collectPlugins(java.util.List<java.lang.String>)
is still called and
org.apache.logging.log4j.plugins.util.PluginRegistry#decodeCacheFiles is still
there so there is nothing really lazy or matching only the configuration
surface and not the full scope of log4j. Hope I didn't miss something.
> 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
> Attachments: image-2020-03-06-08-58-21-169.png, log4j2.png
>
>
> 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.20.1#820001)
