Compare with

Comparison of EclipseLink with Derby server vs Hibernate with Derby server

Each of the following tables focuses on a specific database operation, where the last table presents average results comparison.

Speed comparison of JPA database persistence operations (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
Basic Person Test3.83.83.13.03.43.4
Element Collection Test2.22.01.51.31.81.7
Inheritance Test3.93.42.93.03.43.2
Indexing Test5.24.84.34.14.74.4
Graph (Binary Tree) Test1.91.81.71.61.81.7
Multithreading Test6.16.93.93.95.05.4
All Tests3.83.82.92.83.43.3

The results above show that in general EclipseLink with Derby server is slightly more efficient than Hibernate with Derby server in persisting JPA entity objects to the database.

Speed comparison of JPA database retrieval operations (normalized score, higher is better)

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
Basic Person Test6.43.811.38.48.86.1
Element Collection Test1.81.02.41.02.11.0
Inheritance Test3.73.512.99.78.36.6
Indexing Test3.63.212.89.58.26.4
Graph (Binary Tree) Test0.610.910.731.20.671.1
Multithreading Test8.57.819.813.414.110.6
All Tests4.13.410.07.27.05.3

The results above show that in general EclipseLink with Derby server is more efficient than Hibernate with Derby server in retrieving JPA entity objects from the database.

A large performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of Hibernate with Derby database server (1.0) to the normalized speed of EclipseLink with Derby database server (2.4) reveals that in that case, EclipseLink with Derby server is 2.4 times faster than Hibernate with Derby server.

Speed comparison of JPA database query operations (normalized score, higher is better)

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
Basic Person Test45.834.05.34.125.619.1
Element Collection Test35.233.80.990.6418.117.2
Inheritance Test23.120.55.95.014.512.8
Indexing Test2.52.012.29.27.45.6
Multithreading Test34.336.27.75.121.020.6
All Tests28.225.36.44.817.315.1

The results above show that in general EclipseLink with Derby server is slightly more efficient than Hibernate with Derby server in executing the tested JPA queries.

Speed comparison of JPA database update operations (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
Basic Person Test3.92.94.42.54.12.7
Element Collection Test1.72.31.61.51.61.9
Inheritance Test4.62.96.13.55.33.2
Indexing Test4.53.07.64.26.13.6
Graph (Binary Tree) Test0.701.20.420.580.560.91
Multithreading Test7.36.84.82.56.04.6
All Tests3.83.24.22.54.02.8

The results above show that in general EclipseLink with Derby server is more efficient than Hibernate with Derby server in updating JPA entity objects in the database.

Speed comparison of JPA database removal operations (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
Basic Person Test2.82.93.93.53.33.2
Element Collection Test1.21.70.550.870.871.3
Inheritance Test3.32.93.73.63.53.2
Indexing Test4.93.73.53.64.23.7
Graph (Binary Tree) Test0.510.690.500.700.510.70
Multithreading Test4.86.25.75.15.35.6
All Tests2.93.03.02.93.03.0

The results above show that in general EclipseLink with Derby server is equivalent to Hibernate with Derby server in deleting JPA entity objects from the database.

Comparison of JPA/Database speed - the averages (normalized score, higher is better)

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
EclipseLink
Derby server
Hibernate
Derby server
Basic Person Test12.59.55.64.39.16.9
Element Collection Test8.48.21.41.14.94.6
Inheritance Test7.76.66.35.07.05.8
Indexing Test4.13.38.16.16.14.7
Graph (Binary Tree) Test0.931.20.831.00.881.1
Multithreading Test12.212.88.46.010.39.4
All Tests7.97.15.24.06.65.6

The results above show that in general EclipseLink with Derby server is slightly more efficient than Hibernate with Derby server in performing JPA database operations.

Other Head to Head DBMS/JPA Comparisons