You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Andreas Rytina (JIRA)" <ji...@apache.org> on 2013/04/01 13:29:16 UTC
[jira] [Updated] (LOG4J2-184) the performance for the log4j
initialization needs to be improved
[ https://issues.apache.org/jira/browse/LOG4J2-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Rytina updated LOG4J2-184:
----------------------------------
Description:
The initialization of Log4j 2.0 beta4 via an InputStream takes too long. I attached an small performance test which reproduces the problem. On my machine (Dell Latidude E6530 with an Intel Core i7-3720QM CPU @ 2.6 GHz and 8 GB RAM, OS: Windows 7 64-bit) the test takes approximately one second to complete. On the machine at the customer project, I'm currently working on, it's even worse.
After analyzing this, I found out that the method org.apache.logging.log4j.core.config.plugins.PluginManager.collectPlugins() is called way to often which consumes most time of the initialization!
was:
The initialization of Log4j 2.0 beta4 via an InputStream takes too long. I attached an small performance test which reproduces the problem. On my machine the test takes approximately one second to complete. On the machine at the customer project, I'm currently working on, it's even worse.
After analyzing this, I found out that the method org.apache.logging.log4j.core.config.plugins.PluginManager.collectPlugins() is called way to often which consumes most time of the initialization!
> the performance for the log4j initialization needs to be improved
> -----------------------------------------------------------------
>
> Key: LOG4J2-184
> URL: https://issues.apache.org/jira/browse/LOG4J2-184
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0-beta4
> Reporter: Andreas Rytina
> Attachments: Log4j2InitializationPerformanceTest.java
>
>
> The initialization of Log4j 2.0 beta4 via an InputStream takes too long. I attached an small performance test which reproduces the problem. On my machine (Dell Latidude E6530 with an Intel Core i7-3720QM CPU @ 2.6 GHz and 8 GB RAM, OS: Windows 7 64-bit) the test takes approximately one second to complete. On the machine at the customer project, I'm currently working on, it's even worse.
> After analyzing this, I found out that the method org.apache.logging.log4j.core.config.plugins.PluginManager.collectPlugins() is called way to often which consumes most time of the initialization!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org