Compare with

Comparison of EclipseLink with Derby server vs Hibernate with SQLite embedded

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
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
Basic Person Test3.80.0833.11.03.40.55
Element Collection Test2.20.0671.50.691.80.38
Inheritance Test3.90.0802.90.993.40.54
Indexing Test5.20.0984.31.04.70.55
Graph (Binary Tree) Test1.90.271.70.961.80.61
Multithreading Test6.1failed3.9failed5.0failed
All Tests3.80.122.90.933.40.53

Hibernate with SQLite embedded has failed in 2 tests (see exceptions).

The results above show that in general EclipseLink with Derby server is much more efficient than Hibernate with SQLite embedded in persisting JPA entity objects to the database. Comparing the normalized speed of Hibernate with SQLite embedded database (0.53) to the normalized speed of EclipseLink with Derby database server (3.4) reveals that in these tests, EclipseLink with Derby server is 6.4 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.098) to the normalized speed of EclipseLink with Derby database server (5.2) reveals that in that case, EclipseLink with Derby server is 53.1 times faster than Hibernate with SQLite embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
Basic Person Test6.41.811.31.38.81.5
Element Collection Test1.80.00082.4failed2.10.0008
Inheritance Test3.72.412.91.48.31.9
Indexing Test3.61.912.82.38.22.1
Graph (Binary Tree) Test0.610.560.730.880.670.72
Multithreading Test8.5failed19.8failed14.1failed
All Tests4.11.310.01.57.01.4

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general EclipseLink with Derby server is much more efficient than Hibernate with SQLite embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of Hibernate with SQLite embedded database (1.4) to the normalized speed of EclipseLink with Derby database server (7.0) reveals that in these tests, EclipseLink with Derby server is 5.0 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0008) to the normalized speed of EclipseLink with Derby database server (1.8) reveals that in that case, EclipseLink with Derby server is 2,250 times faster than Hibernate with SQLite embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
Basic Person Test45.81.15.30.2225.60.65
Element Collection Test35.20.390.99failed18.10.39
Inheritance Test23.10.535.90.2814.50.40
Indexing Test2.50.001112.20.437.40.21
Multithreading Test34.3failed7.7failed21.0failed
All Tests28.20.506.40.3117.30.42

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general EclipseLink with Derby server is much more efficient than Hibernate with SQLite embedded in executing the tested JPA queries. Comparing the normalized speed of Hibernate with SQLite embedded database (0.42) to the normalized speed of EclipseLink with Derby database server (17.3) reveals that in these tests, EclipseLink with Derby server is 41.2 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0011) to the normalized speed of EclipseLink with Derby database server (2.5) reveals that in that case, EclipseLink with Derby server is 2,273 times faster than Hibernate with SQLite embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
Basic Person Test3.90.0764.40.654.10.37
Element Collection Test1.70.00221.6failed1.60.0022
Inheritance Test4.60.0796.10.975.30.53
Indexing Test4.50.0577.60.546.10.30
Graph (Binary Tree) Test0.700.260.420.420.560.34
Multithreading Test7.3failed4.8failed6.0failed
All Tests3.80.0944.20.654.00.34

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general EclipseLink with Derby server is much more efficient than Hibernate with SQLite embedded in updating JPA entity objects in the database. Comparing the normalized speed of Hibernate with SQLite embedded database (0.34) to the normalized speed of EclipseLink with Derby database server (4.0) reveals that in these tests, EclipseLink with Derby server is 11.8 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0022) to the normalized speed of EclipseLink with Derby database server (1.7) reveals that in that case, EclipseLink with Derby server is 773 times faster than Hibernate with SQLite embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
Basic Person Test2.80.0613.90.913.30.49
Element Collection Test1.20.00070.55failed0.870.0007
Inheritance Test3.30.0583.70.903.50.48
Indexing Test4.90.0793.50.544.20.31
Graph (Binary Tree) Test0.510.240.500.800.510.52
Multithreading Test4.8failed5.7failed5.3failed
All Tests2.90.0883.00.793.00.40

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general EclipseLink with Derby server is much more efficient than Hibernate with SQLite embedded in deleting JPA entity objects from the database. Comparing the normalized speed of Hibernate with SQLite embedded database (0.40) to the normalized speed of EclipseLink with Derby database server (3.0) reveals that in these tests, EclipseLink with Derby server is 7.5 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0007) to the normalized speed of EclipseLink with Derby database server (1.2) reveals that in that case, EclipseLink with Derby server is 1,714 times faster than Hibernate with SQLite embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
EclipseLink
Derby server
Hibernate
SQLite embedded
Basic Person Test12.50.635.60.819.10.72
Element Collection Test8.40.0921.40.694.90.19
Inheritance Test7.70.636.30.917.00.77
Indexing Test4.10.428.10.966.10.69
Graph (Binary Tree) Test0.930.330.830.770.880.55
Multithreading Test12.2failed8.4failed10.3failed
All Tests7.90.425.20.866.60.62

The results above show that in general EclipseLink with Derby server is much more efficient than Hibernate with SQLite embedded in performing JPA database operations. Comparing the normalized speed of Hibernate with SQLite embedded database (0.62) to the normalized speed of EclipseLink with Derby database server (6.6) reveals that in these tests, EclipseLink with Derby server is 10.6 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.092) to the normalized speed of EclipseLink with Derby database server (8.4) reveals that in that case, EclipseLink with Derby server is 91.3 times faster than Hibernate with SQLite embedded.

Other Head to Head DBMS/JPA Comparisons