Comments on: Java Bean mapper performance tests http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/ Writing about my experiences with technology and all different kinds of projects and experiments Thu, 04 Dec 2008 06:09:31 +0000 By: Christian Schenk http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/#comment-1573 Christian Schenk Tue, 17 Jun 2008 15:21:40 +0000 http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/#comment-1573 Hi AA, you're totally right that the tests aren't <em>that</em> accurate. All I wanted to do was to give some hint about the performance for the various implementations - as you suggest we shouldn't rely on these figures but test the performance in <em>real</em> applications instead for better results. Hi AA,
you’re totally right that the tests aren’t that accurate. All I wanted to do was to give some hint about the performance for the various implementations - as you suggest we shouldn’t rely on these figures but test the performance in real applications instead for better results.

]]> By: AA http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/#comment-1572 AA Tue, 17 Jun 2008 10:38:41 +0000 http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/#comment-1572 I downloaded the sources. There are some issues when measuring the performance this way (PerformanceComparison class): <ul> <li>You should only measure the time it takes to fill the bean with another. Now most of the time is spent in your test code.</li> <li>If you only measure a bean with ints (like the test does) you get different results compared to measuring beans that contain objects (often beans contain more objects than primitives).</li> <li>Hand coded simple class that uses introspection is a lot faster (3x faster) if you cache Methods efficiently and use <code>Method.setAccessible(true)</code>.</li> </ul> So, the results give some hint about what's going on, but I recommend that one should not rely on those figures. I downloaded the sources. There are some issues when measuring the performance this way (PerformanceComparison class):

  • You should only measure the time it takes to fill the bean with another. Now most of the time is spent in your test code.
  • If you only measure a bean with ints (like the test does) you get different results compared to measuring beans that contain objects (often beans contain more objects than primitives).
  • Hand coded simple class that uses introspection is a lot faster (3x faster) if you cache Methods efficiently and use Method.setAccessible(true).

So, the results give some hint about what’s going on, but I recommend that one should not rely on those figures.

]]> By: kwangsu kim http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/#comment-1394 kwangsu kim Thu, 24 Apr 2008 01:53:21 +0000 http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/#comment-1394 thanks for user test. thanks for user test.

]]>