Compare with

Comparison of DataNucleus 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
 DataNucleus
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.40.0592.21.32.80.69
Element Collection Test1.20.0450.641.00.920.52
Inheritance Test3.00.0511.90.852.40.45
Indexing Test5.30.0803.52.34.41.2
Graph (Binary Tree) Test2.1failed1.3failed1.7failed
Multithreading Test10.0failed4.3failed7.2failed
All Tests4.20.0592.31.43.20.71

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

The results above show that in general DataNucleus 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 DataNucleus with H2 database server (3.2) reveals that in these tests, DataNucleus with H2 server is 4.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 H2 database server (5.3) reveals that in that case, DataNucleus with H2 server is 66.2 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 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
Basic Person Test2.50.00475.21.83.90.90
Element Collection Test0.560.00381.11.50.820.77
Inheritance Test2.20.00356.12.24.21.1
Indexing Test2.10.00437.71.84.90.89
Graph (Binary Tree) Test5.7failed8.9failed7.3failed
Multithreading Test2.3failed8.7failed5.5failed
All Tests2.50.00416.31.84.40.91

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

The results above show that in general DataNucleus 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 DataNucleus with H2 database server (4.4) reveals that in these tests, DataNucleus with H2 server is 4.8 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 database server (2.2) reveals that in that case, DataNucleus with H2 server is 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
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
Basic Person Test4.1failed1.3failed2.7failed
Element Collection Test4.0failed0.49failed2.3failed
Inheritance Test2.9failed1.5failed2.2failed
Indexing Test0.0036failed1.5failed0.75failed
Multithreading Test1.3failedfailedfailed1.3failed
All Tests2.5failed1.2failed1.9failed

DataNucleus with H2 server 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
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
Basic Person Test2.50.0121.40.761.90.39
Element Collection Test2.00.0121.01.11.50.53
Inheritance Test2.40.0112.30.812.30.41
Indexing Test2.70.0113.01.32.90.64
Graph (Binary Tree) Test1.8failed0.60failed1.2failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests2.30.0121.70.972.00.49

DataNucleus with H2 server 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 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 DataNucleus with H2 database server (2.0) reveals that in these tests, DataNucleus with H2 server is 4.1 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 database server (2.7) reveals that in that case, DataNucleus with H2 server is 245 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 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.40.0111.31.52.30.74
Element Collection Test1.50.0100.681.61.10.80
Inheritance Test2.70.00931.31.12.00.57
Indexing Test5.70.0171.92.13.81.1
Graph (Binary Tree) Test1.5failed1.2failed1.3failed
Multithreading Testfailedfailed5.1failed5.1failed
All Tests3.00.0121.91.62.40.79

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

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

On the other hand, DataNucleus with H2 server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (0.68) to the normalized speed of DataNucleus with DB4O embedded database (1.6) reveals that in that case, DataNucleus with H2 server is 2.4 times slower than DataNucleus with DB4O embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
DataNucleus
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.20.0222.31.32.70.68
Element Collection Test1.90.0180.781.31.30.66
Inheritance Test2.60.0192.61.22.60.63
Indexing Test3.20.0283.51.93.30.94
Graph (Binary Tree) Test2.8failed3.0failed2.9failed
Multithreading Test4.5failed6.0failed5.3failed
All Tests2.90.0222.81.42.90.73

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

A huge performance gap has been detected when using simple basic entities with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.022) to the normalized speed of DataNucleus with H2 database server (3.2) reveals that in that case, DataNucleus with H2 server is 145 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons