More on JPA Performance

I used my free day to do some more performance benchmarking using EJB 3.0 and WebServices. As I wrote in my last blog entry on this topic, I was astonished what performance is possible even in a VM on my cheat laptop. But now I invested some more time to tune my laptop (running JkDefrag gave its disk an amazing push) and do an optimization in the application itself: Using precompiled queries (so-called "named queries" in JPA) instead of dynamic queries. My idea was that a precompiled query should run much faster since the machine can spare the time for parsing the JPA-QL string. In addition, I changed the benchmarking tool that I wrote to use multiple threads to simulate five clients instead of only one, and to run 50.000 loops to remove Java's typical warmup delay. This should better simulate the real world. Actually it seems that these optimizations are very beneficial to the overall performance, as the current version of the benchmark shows: 200 "senseless" calls (no serverside workload, just an empty SOAP roundtrip) need half a second. While this is an acceptable (and taking into account the fact that extensive XML parsing is done for the WebService, quite impressive) number, compared to the following numbers shows that half the time of virtually each method call, is eaten up by "beeing a WebService" itself. 200 "INSERTs" (using JPA via SOAP) nee...

Date: January, 03 2010
Url: http://www.java.net/blog/mkarg/archive/2010/01/03/more-jpa-performance

Others News