Compare with

Comparison of DataNucleus with Derby 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
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
Basic Person Test2.80.0592.31.32.60.69
Element Collection Test0.710.0450.351.00.530.52
Inheritance Test2.70.0512.00.852.30.45
Indexing Test4.50.0804.02.34.31.2
Graph (Binary Tree) Test0.62failed0.53failed0.57failed
Multithreading Test4.9failed3.4failed4.1failed
All Tests2.70.0592.11.42.40.71

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

The results above show that in general DataNucleus with Derby 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 Derby database server (2.4) reveals that in these tests, DataNucleus with Derby server is 3.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.080) to the normalized speed of DataNucleus with Derby database server (4.5) reveals that in that case, DataNucleus with Derby server is 56.2 times faster than DataNucleus with DB4O embedded.

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
Basic Person Test0.560.00476.31.83.40.90
Element Collection Test0.360.00380.931.50.640.77
Inheritance Test0.450.00356.82.23.61.1
Indexing Test0.500.00437.11.83.80.89
Graph (Binary Tree) Test0.22failed6.6failed3.4failed
Multithreading Test1.2failed10.0failed5.6failed
All Tests0.550.00416.31.83.40.91

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

The results above show that in general DataNucleus with Derby 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 Derby database server (3.4) reveals that in these tests, DataNucleus with Derby server is 3.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 retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0035) to the normalized speed of DataNucleus with Derby database server (0.45) reveals that in that case, DataNucleus with Derby server is 129 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
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
Basic Person Test37.7failed3.6failed20.7failed
Element Collection Test25.9failed1.4failed13.6failed
Inheritance Test6.5failed1.8failed4.2failed
Indexing Test0.030failed4.9failed2.5failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests17.5failed2.9failed10.2failed

DataNucleus with Derby server has failed in 2 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
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
Basic Person Test1.10.0120.850.760.990.39
Element Collection Test0.810.0120.621.10.710.53
Inheritance Test1.20.0111.30.811.20.41
Indexing Test1.20.0111.51.31.30.64
Graph (Binary Tree) Test0.29failed0.41failed0.35failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests0.930.0120.920.970.920.49

DataNucleus with Derby 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 Derby server is more efficient than DataNucleus with DB4O embedded in updating JPA entity objects in the database.

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 DataNucleus with Derby database server (1.2) reveals that in that case, DataNucleus with Derby server is 109 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
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
Basic Person Test1.30.0111.31.51.30.74
Element Collection Test0.610.0100.331.60.470.80
Inheritance Test1.00.00931.31.11.20.57
Indexing Test2.30.0171.92.12.11.1
Graph (Binary Tree) Test0.26failed0.46failed0.36failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests1.10.0121.11.61.10.79

DataNucleus with Derby 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 Derby server is more efficient than DataNucleus with DB4O embedded in deleting JPA entity objects from the database.

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 Derby database server (2.3) reveals that in that case, DataNucleus with Derby server is 135 times faster than DataNucleus with DB4O embedded.

On the other hand, DataNucleus with Derby server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.33) to the normalized speed of DataNucleus with DB4O embedded database (1.6) reveals that in that case, DataNucleus with Derby server is 4.8 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
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
DataNucleus
Derby server
DataNucleus
DB4O embedded
Basic Person Test8.70.0222.91.35.80.68
Element Collection Test5.70.0180.721.33.20.66
Inheritance Test2.40.0192.61.22.50.63
Indexing Test1.70.0283.91.92.80.94
Graph (Binary Tree) Test0.35failed2.0failed1.2failed
Multithreading Test3.0failed6.7failed4.9failed
All Tests3.80.0222.81.43.30.73

The results above show that in general DataNucleus with Derby 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 Derby database server (3.3) reveals that in these tests, DataNucleus with Derby server is 4.5 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 Derby database server (8.7) reveals that in that case, DataNucleus with Derby server is 395 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons