[
https://issues.apache.org/jira/browse/LOG4J2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510169#comment-17510169
]
Matt Sicker commented on LOG4J2-2795:
-------------------------------------
I'd imagine a lot of the static init stuff was for aggressive caching which
made more sense for long-running applications. Now that there's a proper IoC
container, a lot of that can be refactored, though I'll have to find the
applicable code first!
If there's a lot of time spent waiting on locks from lazy-initialized objects,
then that would be interesting to know.
Do you have any test code for this? Or are you just timing the launch of a
trivial app with log4j in it?
> 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)
