Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.8.6
-
JDK 1.6
-
Novice
Description
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.