[
https://issues.apache.org/jira/browse/CAMEL-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468416#comment-13468416
]
Claus Ibsen commented on CAMEL-5675:
------------------------------------
Well even with some caching it only speedup for very big routes.
Les, can you tell us a bit about your setup? How many tests do you run? Do you
have many routes, and are they small/big etc?
And do you have JMX enabled during testing?
For the Camel tests of itself there is hardly a speedup (many small route
tests). And most tests have disabled JMX.
For a big route with 1000 nodes and JMX enabled, I could cut down startup time
with 1.5-2s. But just wonder who would have such big routes?
> 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