Compare with

Comparison of DataNucleus with Derby 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
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
Basic Person Test4.60.0592.81.33.70.69
Element Collection Test2.40.0451.61.02.00.52
Inheritance Test4.60.0512.70.853.70.45
Indexing Test7.60.0804.82.36.21.2
Graph (Binary Tree) Test1.6failed1.4failed1.5failed
Multithreading Test8.6failed3.3failed5.9failed
All Tests4.90.0592.81.43.80.71

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

The results above show that in general DataNucleus with Derby 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 Derby embedded database (3.8) reveals that in these tests, DataNucleus with Derby embedded 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.080) to the normalized speed of DataNucleus with Derby embedded database (7.6) reveals that in that case, DataNucleus with Derby embedded is 95.0 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
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
Basic Person Test6.80.004714.91.810.90.90
Element Collection Test5.40.00387.61.56.50.77
Inheritance Test8.80.003514.82.211.81.1
Indexing Test9.20.004314.11.811.60.89
Graph (Binary Tree) Test9.9failed15.8failed12.9failed
Multithreading Test11.9failed11.5failed11.7failed
All Tests8.70.004113.11.810.90.91

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

The results above show that in general DataNucleus with Derby 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 Derby embedded database (10.9) reveals that in these tests, DataNucleus with Derby embedded is 12.0 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 embedded database (8.8) reveals that in that case, DataNucleus with Derby embedded is 2,514 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 embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
Basic Person Test39.1failed7.5failed23.3failed
Element Collection Test46.0failed6.7failed26.3failed
Inheritance Test7.7failed3.8failed5.7failed
Indexing Test0.053failed8.0failed4.0failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests23.2failed6.5failed14.8failed

DataNucleus with Derby embedded 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 embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
Basic Person Test4.00.0123.80.763.90.39
Element Collection Test3.70.0124.51.14.10.53
Inheritance Test4.40.0114.80.814.60.41
Indexing Test5.20.0114.21.34.70.64
Graph (Binary Tree) Test2.7failed1.5failed2.1failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests4.00.0123.70.973.90.49

DataNucleus with Derby 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 Derby 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 Derby embedded database (3.9) reveals that in these tests, DataNucleus with Derby embedded is 8.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.011) to the normalized speed of DataNucleus with Derby embedded database (5.2) reveals that in that case, DataNucleus with Derby embedded is 473 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 embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
Basic Person Test3.50.0111.31.52.40.74
Element Collection Test1.90.0101.61.61.70.80
Inheritance Test2.40.00931.31.11.90.57
Indexing Test6.60.0171.92.14.31.1
Graph (Binary Tree) Test0.81failed0.93failed0.87failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests3.00.0121.41.62.20.79

DataNucleus with Derby 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 Derby embedded is 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 Derby embedded database (2.2) reveals that in these tests, DataNucleus with Derby embedded is 2.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.017) to the normalized speed of DataNucleus with Derby embedded database (6.6) reveals that in that case, DataNucleus with Derby embedded is 388 times faster than DataNucleus with DB4O embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
Basic Person Test53.335.153.335.453.335.2
Element Collection Test42.629.542.629.942.629.7
Inheritance Test48.133.448.133.548.133.4
Indexing Test62.341.063.341.962.841.5
Graph (Binary Tree) Test13.6failed10.2failed11.9failed
Multithreading Test52.0failed8.0failed30.0failed
All Tests45.334.837.635.241.535.0

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
DataNucleus
Derby embedded
DataNucleus
DB4O embedded
Basic Person Test11.60.0226.11.38.80.68
Element Collection Test11.90.0184.41.38.10.66
Inheritance Test5.60.0195.51.25.50.63
Indexing Test5.70.0286.61.96.20.94
Graph (Binary Tree) Test3.7failed4.9failed4.3failed
Multithreading Test10.3failed7.4failed8.8failed
All Tests8.00.0225.71.46.90.73

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

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.018) to the normalized speed of DataNucleus with Derby embedded database (11.9) reveals that in that case, DataNucleus with Derby embedded is 661 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons