Compare with

Comparison of DataNucleus with HSQLDB 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
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
Basic Person Test14.20.0594.81.39.50.69
Element Collection Test6.60.0452.11.04.30.52
Inheritance Test13.60.0514.60.859.10.45
Indexing Test24.60.08011.12.317.81.2
Graph (Binary Tree) Test6.8failed4.5failed5.7failed
Multithreading Test38.5failed8.5failed23.5failed
All Tests17.40.0595.91.411.70.71

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

The results above show that in general DataNucleus with HSQLDB 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 HSQLDB embedded database (11.7) reveals that in these tests, DataNucleus with HSQLDB embedded is 16.5 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.080) to the normalized speed of DataNucleus with HSQLDB embedded database (24.6) reveals that in that case, DataNucleus with HSQLDB embedded is 308 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
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
Basic Person Test6.60.004710.21.88.40.90
Element Collection Test3.60.00388.11.55.80.77
Inheritance Test5.70.00358.82.27.21.1
Indexing Test5.10.00439.51.87.30.89
Graph (Binary Tree) Test7.2failed9.3failed8.3failed
Multithreading Test8.1failed9.5failed8.8failed
All Tests6.00.00419.21.87.60.91

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

The results above show that in general DataNucleus with HSQLDB 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 HSQLDB embedded database (7.6) reveals that in these tests, DataNucleus with HSQLDB embedded is 8.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 HSQLDB embedded database (5.7) reveals that in that case, DataNucleus with HSQLDB embedded is 1,629 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
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
Basic Person Test1.4failed0.48failed0.95failed
Element Collection Test1.3failed0.67failed1.0failed
Inheritance Test1.6failed0.61failed1.1failed
Indexing Test0.0016failed0.63failed0.32failed
Multithreading Test0.40failedfailedfailed0.40failed
All Tests0.96failed0.60failed0.80failed

DataNucleus with HSQLDB embedded has failed in 1 tests (see exceptions). 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
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
Basic Person Test11.50.0122.70.767.10.39
Element Collection Test6.90.0122.71.14.80.53
Inheritance Test10.30.0113.60.816.90.41
Indexing Test11.40.0114.41.37.90.64
Graph (Binary Tree) Test3.5failed1.5failed2.5failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests8.70.0123.00.975.80.49

DataNucleus with HSQLDB 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 HSQLDB 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 HSQLDB embedded database (5.8) reveals that in these tests, DataNucleus with HSQLDB embedded is 11.8 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 HSQLDB embedded database (11.4) reveals that in that case, DataNucleus with HSQLDB embedded is 1,036 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
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB 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) Test2.9failed2.0failed2.5failed
Multithreading Test40.1failed13.7failed26.9failed
All Tests10.60.0123.71.67.10.79

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

The results above show that in general DataNucleus with HSQLDB 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 HSQLDB embedded database (7.1) reveals that in these tests, DataNucleus with HSQLDB embedded is 9.0 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 HSQLDB embedded database (4.9) reveals that in that case, DataNucleus with HSQLDB 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
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
Basic Person Test41.435.141.435.441.435.2
Element Collection Test23.429.523.429.923.429.7
Inheritance Test41.433.441.433.541.433.4
Indexing Test48.441.049.241.948.841.5
Graph (Binary Tree) Test12.5failed9.4failed10.9failed
Multithreading Test51.9failed10.3failed31.1failed
All Tests36.534.829.235.232.935.0

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
DataNucleus
HSQLDB embedded
DataNucleus
DB4O embedded
Basic Person Test7.60.0223.91.35.70.68
Element Collection Test4.70.0183.01.33.80.66
Inheritance Test7.10.0193.81.25.40.63
Indexing Test9.70.0285.51.97.60.94
Graph (Binary Tree) Test5.1failed4.3failed4.7failed
Multithreading Test21.8failed10.6failed17.0failed
All Tests9.00.0224.81.47.00.73

The results above show that in general DataNucleus with HSQLDB 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 HSQLDB embedded database (7.0) reveals that in these tests, DataNucleus with HSQLDB embedded is 9.6 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 HSQLDB embedded database (7.1) reveals that in that case, DataNucleus with HSQLDB embedded is 374 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons