Compare with

Comparison of DataNucleus with H2 embedded 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
 DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test19.20.0598.01.313.60.69
Element Collection Test6.60.0452.81.04.70.52
Inheritance Test15.60.0514.40.8510.00.45
Indexing Test24.40.08011.82.318.11.2
Graph (Binary Tree) Test9.2failed6.2failed7.7failed
Multithreading Test34.9failed7.1failed21.0failed
All Tests18.30.0596.71.412.50.71

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

The results above show that in general DataNucleus with H2 embedded 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 DataNucleus with H2 embedded database (12.5) reveals that in these tests, DataNucleus with H2 embedded is 17.6 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.059) to the normalized speed of DataNucleus with H2 embedded database (19.2) reveals that in that case, DataNucleus with H2 embedded is 325 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
 DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test13.20.004713.51.813.30.90
Element Collection Test6.40.00388.91.57.70.77
Inheritance Test12.20.003512.72.212.41.1
Indexing Test8.10.004316.51.812.30.89
Graph (Binary Tree) Test10.6failed20.9failed15.8failed
Multithreading Test13.3failed9.9failed11.6failed
All Tests10.60.004113.71.812.20.91

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

The results above show that in general DataNucleus with H2 embedded 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 DataNucleus with H2 embedded database (12.2) reveals that in these tests, DataNucleus with H2 embedded is 13.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 DataNucleus with H2 embedded database (12.2) reveals that in that case, DataNucleus with H2 embedded is 3,486 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
 DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test4.7failed1.4failed3.1failed
Element Collection Test5.0failed2.4failed3.7failed
Inheritance Test3.8failed1.6failed2.7failed
Indexing Test0.0041failed1.8failed0.91failed
Multithreading Test1.2failed0.79failed1.0failed
All Tests3.0failed1.6failed2.3failed

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
 DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test10.00.0123.90.766.90.39
Element Collection Test7.60.0123.91.15.80.53
Inheritance Test9.40.0114.40.816.90.41
Indexing Test10.60.0115.91.38.20.64
Graph (Binary Tree) Test5.9failed3.7failed4.8failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests8.70.0124.40.976.50.49

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

The results above show that in general DataNucleus with H2 embedded 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 DataNucleus with H2 embedded database (6.5) reveals that in these tests, DataNucleus with H2 embedded is 13.3 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.011) to the normalized speed of DataNucleus with H2 embedded database (10.6) reveals that in that case, DataNucleus with H2 embedded is 964 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
 DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test4.20.0111.31.52.80.74
Element Collection Test4.90.0101.61.63.20.80
Inheritance Test4.00.00931.31.12.70.57
Indexing Test7.50.0171.92.14.71.1
Graph (Binary Tree) Test5.6failed4.1failed4.8failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests5.20.0122.01.63.60.79

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

The results above show that in general DataNucleus with H2 embedded 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 DataNucleus with H2 embedded database (3.6) reveals that in these tests, DataNucleus with H2 embedded is 4.6 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.010) to the normalized speed of DataNucleus with H2 embedded database (4.9) reveals that in that case, DataNucleus with H2 embedded is 490 times faster than DataNucleus with DB4O embedded.

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test27.035.127.035.427.035.2
Element Collection Test22.429.522.429.922.429.7
Inheritance Test27.033.427.033.527.033.4
Indexing Test31.641.032.141.931.941.5
Graph (Binary Tree) Test20.0failed15.0failed17.5failed
Multithreading Test33.9failed9.2failed21.5failed
All Tests27.034.822.135.224.635.0

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

The results above show that in general DataNucleus with DB4O embedded is more efficient than DataNucleus with H2 embedded in using disk space.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
DataNucleus
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test10.30.0225.61.37.90.68
Element Collection Test6.10.0183.91.35.00.66
Inheritance Test9.00.0194.91.26.90.63
Indexing Test10.10.0287.61.98.90.94
Graph (Binary Tree) Test7.8failed8.7failed8.3failed
Multithreading Test16.5failed5.9failed11.2failed
All Tests9.60.0226.01.47.80.73

The results above show that in general DataNucleus with H2 embedded 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 DataNucleus with H2 embedded database (7.8) reveals that in these tests, DataNucleus with H2 embedded is 10.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/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.019) to the normalized speed of DataNucleus with H2 embedded database (9.0) reveals that in that case, DataNucleus with H2 embedded is 474 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons