Compare with

Comparison of DataNucleus with H2 server vs EclipseLink 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
 DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
Basic Person Test3.40.0742.20.902.80.49
Element Collection Test1.20.0610.640.650.920.36
Inheritance Test3.00.0831.90.822.40.45
Indexing Test5.30.113.51.64.40.87
Graph (Binary Tree) Test2.10.241.30.911.70.57
Multithreading Test10.00.104.32.17.21.1
All Tests4.20.112.31.23.20.64

The results above show that in general DataNucleus with H2 server is much more efficient than EclipseLink with SQLite embedded in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.64) to the normalized speed of DataNucleus with H2 database server (3.2) reveals that in these tests, DataNucleus with H2 server is 5.0 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.10) to the normalized speed of DataNucleus with H2 database server (10.0) reveals that in that case, DataNucleus with H2 server is 100 times faster than EclipseLink with SQLite embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
Basic Person Test2.5failed5.2failed3.9failed
Element Collection Test0.560.00071.1failed0.820.0007
Inheritance Test2.2failed6.1failed4.2failed
Indexing Test2.1failed7.7failed4.9failed
Graph (Binary Tree) Test5.7failed8.9failed7.3failed
Multithreading Test2.3failed8.7failed5.5failed
All Tests2.50.00076.3failed4.40.0007

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
Basic Person Test4.11.21.3failed2.71.2
Element Collection Test4.00.290.49failed2.30.29
Inheritance Test2.90.691.5failed2.20.69
Indexing Test0.00360.00081.5failed0.750.0008
Multithreading Test1.3failedfailedfailed1.3failed
All Tests2.50.551.2failed1.90.55

DataNucleus with H2 server has failed in 1 tests (see exceptions). EclipseLink with SQLite embedded has failed in 6 tests (see exceptions).

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
Basic Person Test2.5failed1.4failed1.9failed
Element Collection Test2.00.00161.0failed1.50.0016
Inheritance Test2.4failed2.3failed2.3failed
Indexing Test2.7failed3.0failed2.9failed
Graph (Binary Tree) Test1.8failed0.60failed1.2failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests2.30.00161.7failed2.00.0016

DataNucleus with H2 server has failed in 2 tests (see exceptions). EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
Basic Person Test3.4failed1.3failed2.3failed
Element Collection Test1.50.00060.68failed1.10.0006
Inheritance Test2.7failed1.3failed2.0failed
Indexing Test5.7failed1.9failed3.8failed
Graph (Binary Tree) Test1.5failed1.2failed1.3failed
Multithreading Testfailedfailed5.1failed5.1failed
All Tests3.00.00061.9failed2.40.0006

DataNucleus with H2 server has failed in 1 tests (see exceptions). EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
DataNucleus
H2 server
EclipseLink
SQLite embedded
Basic Person Test3.20.662.30.902.70.74
Element Collection Test1.90.0700.780.651.30.17
Inheritance Test2.60.382.60.822.60.53
Indexing Test3.20.0583.51.63.30.58
Graph (Binary Tree) Test2.80.243.00.912.90.57
Multithreading Test4.50.106.02.15.31.1
All Tests2.90.222.81.22.90.52

The results above show that in general DataNucleus with H2 server is much more efficient than EclipseLink with SQLite embedded in performing JPA database operations. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.52) to the normalized speed of DataNucleus with H2 database server (2.9) reveals that in these tests, DataNucleus with H2 server is 5.6 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.058) to the normalized speed of DataNucleus with H2 database server (3.2) reveals that in that case, DataNucleus with H2 server is 55.2 times faster than EclipseLink with SQLite embedded.

Other Head to Head DBMS/JPA Comparisons