You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/07/04 12:00:00 UTC
[jira] [Commented] (CAMEL-11321) Can CamelContext startup faster
[ https://issues.apache.org/jira/browse/CAMEL-11321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073529#comment-16073529 ]
Claus Ibsen commented on CAMEL-11321:
-------------------------------------
camel-spring-boot in the auto configuration creates a ProducerTemplate and ConsumerTemplate bean which may not be in-use / needed. We can look at optimising to only create them on demand, or to lazy init the bean on use etc, as its startup time cost a bit with the caffine cache
> Can CamelContext startup faster
> -------------------------------
>
> Key: CAMEL-11321
> URL: https://issues.apache.org/jira/browse/CAMEL-11321
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-spring-boot
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> [~lb] have some thoughts on if we can make CamelContext startup faster, especially when using Spring Boot. Spring Boot itself is not so fast, but should be faster in 2.x.
> For example we could consider camel-core to not do any classpath scanning for components that are provided OOTB in camel-core, eg if using "log" endpoint, then only check the spring registry if any custom bean of that, and if not, then we know "log" is from camel-core and then we know its class name already and dont need to scan the classpath.
> We could take that one step further for the entire Camel release and have a plugin that generate/keep java source file up to date from camel-core, which has complete mapping of all component-name=component-class.
> We can also do some profiling and see if there is some hot-spots. There is also the revised work that Zoran does in starting Camel on spring / spring-boot.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)