[
https://issues.apache.org/jira/browse/CAMEL-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13675:
--------------------------------
Description:
This method takes approx 60 millis on my laptop
org.apache.camel.main.DefaultConfigurationConfigurer#afterPropertiesSet
I suspects its all those lambda's that are loaded on classpath and only in use
if there is a bean to lookup. The logic can be improved to use old fashioned
code with some if != null
If I disable all of those then its down to 4 millis on my laptop
was:
This method takes approx 60 millis on my laptop
org.apache.camel.main.DefaultConfigurationConfigurer#afterPropertiesSet
I suspects its all those lambda's that are loaded on classpath and only in use
if there is a bean to lookup. The logic can be improved to use old fashioned
code with some if != null
> camel-main - Optimise main configurer
> -------------------------------------
>
> Key: CAMEL-13675
> URL: https://issues.apache.org/jira/browse/CAMEL-13675
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> This method takes approx 60 millis on my laptop
> org.apache.camel.main.DefaultConfigurationConfigurer#afterPropertiesSet
> I suspects its all those lambda's that are loaded on classpath and only in
> use if there is a bean to lookup. The logic can be improved to use old
> fashioned code with some if != null
> If I disable all of those then its down to 4 millis on my laptop
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
