ORM solutions (JPA; Hibernate) vs. JDBC

Posted by Grasper on Stack Overflow See other posts from Stack Overflow or by Grasper
Published on 2008-11-04T02:25:33Z Indexed on 2010/04/20 8:43 UTC
Read the original article Hit count: 298

Filed under:
|
|
|
|

I need to be able to insert/update objects at a consistent rate of at least 8000 objects every 5 seconds in an in-memory HSQL database.

I have done some comparison performance testing between Spring/Hibernate/JPA and pure JDBC. I have found a significant difference in performance using HSQL.. With Spring/Hib/JPA, I can insert 3000-4000 of my 1.5 KB objects (with a One-Many and a Many-Many relationship) in 5 seconds, while with direct JDBC calls I can insert 10,000-12,000 of those same objects.

I cannot figure out why there is such a huge discrepancy. I have tweaked the Spring/Hib/JPA settings a lot trying to get close in performance without luck. I want to use Spring/Hib/JPA for future purposes, expandability, and because the foreign key relationships (one-many and many-many) are difficult to maintain by hand; but the performance requirements seem to point towards using pure JDBC.

Any ideas of why there would be such a huge discrepancy?

© Stack Overflow or respective owner

Related posts about hibernate

Related posts about jpa