Compare with

Comparison of EclipseLink with H2 server vs DataNucleus with DB4O 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
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
Basic Person Test5.60.0592.51.34.00.69
Element Collection Test4.20.0451.51.02.80.52
Inheritance Test6.60.0512.10.854.40.45
Indexing Test9.70.0804.12.36.91.2
Graph (Binary Tree) Test4.7failed3.5failed4.1failed
Multithreading Test10.2failed4.0failed7.1failed
All Tests6.80.0592.91.44.90.71

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.051) to the normalized speed of EclipseLink with H2 database server (6.6) reveals that in that case, EclipseLink with H2 server is 129 times faster than DataNucleus with DB4O embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
Basic Person Test5.50.00478.21.86.80.90
Element Collection Test3.20.00384.21.53.70.77
Inheritance Test4.70.003510.12.27.41.1
Indexing Test4.40.00439.41.86.90.89
Graph (Binary Tree) Test1.1failed1.9failed1.5failed
Multithreading Test12.2failed15.9failed14.0failed
All Tests5.20.00418.31.86.70.91

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general EclipseLink with H2 server is much more efficient than DataNucleus with DB4O embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.91) to the normalized speed of EclipseLink with H2 database server (6.7) reveals that in these tests, EclipseLink with H2 server is 7.4 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0035) to the normalized speed of EclipseLink with H2 database server (4.7) reveals that in that case, EclipseLink with H2 server is 1,343 times faster than DataNucleus with DB4O embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.8failed1.1failed2.5failed
Element Collection Test4.1failed1.1failed2.6failed
Inheritance Test3.2failed1.3failed2.3failed
Indexing Test3.0failed8.0failed5.5failed
Multithreading Test1.1failed1.0failed1.1failed
All Tests3.0failed2.5failed2.8failed

DataNucleus with DB4O embedded has failed in 10 tests (see exceptions).

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
Basic Person Test4.50.0122.20.763.40.39
Element Collection Test3.80.0122.41.13.10.53
Inheritance Test4.40.0113.00.813.70.41
Indexing Test4.20.0113.11.33.70.64
Graph (Binary Tree) Test1.4failed0.79failed1.1failed
Multithreading Test7.8failed2.5failed5.1failed
All Tests4.30.0122.30.973.30.49

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general EclipseLink with H2 server is much more efficient than DataNucleus with DB4O embedded in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.49) to the normalized speed of EclipseLink with H2 database server (3.3) reveals that in these tests, EclipseLink with H2 server is 6.7 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.011) to the normalized speed of EclipseLink with H2 database server (4.4) reveals that in that case, EclipseLink with H2 server is 400 times faster than DataNucleus with DB4O embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
Basic Person Test6.40.0113.11.54.80.74
Element Collection Test3.00.0101.31.62.20.80
Inheritance Test5.60.00932.81.14.20.57
Indexing Test10.30.0173.82.17.01.1
Graph (Binary Tree) Test1.5failed1.3failed1.4failed
Multithreading Test7.0failed4.9failed6.0failed
All Tests5.60.0122.91.64.30.79

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general EclipseLink with H2 server is much more efficient than DataNucleus with DB4O embedded in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.79) to the normalized speed of EclipseLink with H2 database server (4.3) reveals that in these tests, EclipseLink with H2 server is 5.4 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.017) to the normalized speed of EclipseLink with H2 database server (10.3) reveals that in that case, EclipseLink with H2 server is 606 times faster than DataNucleus with DB4O embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
EclipseLink
H2 server
DataNucleus
DB4O embedded
Basic Person Test5.20.0223.41.34.30.68
Element Collection Test3.60.0182.11.32.90.66
Inheritance Test4.90.0193.91.24.40.63
Indexing Test6.30.0285.71.96.00.94
Graph (Binary Tree) Test2.1failed1.9failed2.0failed
Multithreading Test7.7failed5.7failed6.7failed
All Tests5.10.0223.81.44.50.73

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.019) to the normalized speed of EclipseLink with H2 database server (4.9) reveals that in that case, EclipseLink with H2 server is 258 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons