You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Romain Manni-Bucau (Jira)" <ji...@apache.org> on 2020/03/03 07:15:00 UTC

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

     [ https://issues.apache.org/jira/browse/LOG4J2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau updated LOG4J2-2795:
---------------------------------------
    Attachment: log4j2.png

> 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)