JPA implementations comparison: Hibernate, Toplink Essentials, Openjpa, Eclipselink

Markus Eisele
Found an article about performance comparison for the most well known Java Persistence API (JPA) implementations: Toplink Essentials, EclipseLink, Hibernate and OpenJPA.

Summarized conclusions: (taken from the articel)

  1. There is not an implementation that clearly has the best performance. Some had a very good CPU or memory performance and some did it very well when inserting or querying. But none of them was outstanding as a whole.

  2. The number of records inserted by Hibernate was extremely higher than it was for any other implementation (4 times more compared to Eclipselink and 24 times more compared to OpenJPA). However, Hibernate was also the JPA implementation that executed the lowest number of queries, although the differences in this value (3080 for Hibernate vs 3740 for Toplink Essentials) are not so extreme as for the number of inserts.

  3. Hibernate was also the implementation that consumed more memory. But having into account that it inserted many more records than the others, it sounds reasonable.

  4. OpenJPA had the lowest value of inserts+queries.

  5. The number of inserts executed by OpenJPA was extremely low, compared to the others.

  6. The usage of CPU in the case of Toplink Essentials and Eclipselink was extremely low.

read the full article here

Post a Comment


  1. I think it needs to be noted that the referenced blog posting is an out of the box performance test.

    An out of the box, no tuning performance test isn't a realistic performance test.

Post a Comment