[
https://issues.apache.org/jira/browse/CAMEL-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467779#comment-13467779
]
Claus Ibsen commented on CAMEL-5675:
------------------------------------
Yeah I think we could have caching during startup of CamelContext. Having cache
at runtime is a bit more problematic, as you would need to be able to limit the
cache size. And as well have soft reference to avoid classloader issues etc.
Its easier to cache during startup only (and during shutdown as well) as we can
control when caching is enabled/disable.
> Camel Route Startup Performance Slow
> ------------------------------------
>
> Key: CAMEL-5675
> URL: https://issues.apache.org/jira/browse/CAMEL-5675
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.8.6
> Environment: JDK 1.6
> Reporter: Les Novell
> Assignee: Claus Ibsen
> Labels: performance
>
> I am writing unit tests for Camel and found that each unit test was taking up
> to a second just to create the Camel routes. That's not very long, but we
> have a large unit test suite that needs to run quickly.
> I did a performance profile and found that most of the time is going to the
> method org.apache.camel.util.IntrospectionSupport.getProperties(Object, Map,
> String). That method, then also calls IntrospectionSupport.isSetter(Method),
> and just running two unit tests I saw isSettter called 2.5 million times!
> It seems to me that a cache per class of the properties would make a huge
> performance improvement on Camel route building.
--
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