[
https://issues.apache.org/jira/browse/LOG4J2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051845#comment-17051845
]
Romain Manni-Bucau commented on LOG4J2-2795:
--------------------------------------------
Even if it is true most JVM will have JIT, it still does not justify this
slowness. Concretely just adding log4j - so not changing anything to your
functional - makes your single test passing from 30ms to > 1s which is likely
not acceptable just for logs. Indeed it is possible to exclude log4j to use
something else most of the time but I don't see a reason it is that slow to
init - in particular when you know a CDI container starts 3-4 faster. This is
why i reported this issue.
> 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: 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.3.4#803005)
