[
https://issues.apache.org/jira/browse/CAMEL-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-5675:
-------------------------------
Attachment: CAMEL-5675.patch
I have attached a patch which has caching on JMX and IntrospectionSupport.
The most noticeable performance improvements is when JMX is enabled, and if you
have large routes.
The big route tests is about cut down from 8s to 4s on startup (looking at the
startup time Camel reports itself).
> 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
> Attachments: CAMEL-5675.patch
>
>
> 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