[
https://issues.apache.org/jira/browse/LOG4J2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510073#comment-17510073
]
Romain Manni-Bucau commented on LOG4J2-2795:
--------------------------------------------
[~mattsicker] I didn't reprofile it since the ton of static inits is one of the
issue and requires a drastical change in the code. Technically a single
singleton - manager or context - abusing of static data is needed (rest are
plain instances with fields) so think using the internal reflection-less IoC to
align the code design on something more modern and less time consuming at
startup can be worth it to solve this issue. Taking 10 times more than an
actual IoC is weirdish to get logs ;).
> 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)
