Compare with

Comparison of DataNucleus with Derby server vs ObjectDB 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
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embedded
Basic Person Test2.81002.31002.6100
Element Collection Test0.711000.351000.53100
Inheritance Test2.71002.01002.3100
Indexing Test4.51004.01004.3100
Graph (Binary Tree) Test0.6288.40.531000.5794.2
Multithreading Test4.91003.41004.1100
All Tests2.798.12.11002.499.0

The results above show that in general ObjectDB embedded is much more efficient than DataNucleus with Derby server in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with Derby database server (2.4) to the normalized speed of ObjectDB embedded database (99.0) reveals that in these tests, ObjectDB embedded is 41.2 times faster than DataNucleus with Derby server.

A huge performance gap has been detected 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 ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 286 times faster than DataNucleus with Derby server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embedded
Basic Person Test0.561006.31003.4100
Element Collection Test0.361000.931000.64100
Inheritance Test0.451006.81003.6100
Indexing Test0.501007.11003.8100
Graph (Binary Tree) Test0.221006.61003.4100
Multithreading Test1.210010.01005.6100
All Tests0.551006.31003.4100

The results above show that in general ObjectDB embedded is much more efficient than DataNucleus with Derby server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby database server (3.4) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 29.4 times faster than DataNucleus with Derby server.

A huge performance gap has been detected when using graphs of objects with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.22) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 455 times faster than DataNucleus with Derby server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embedded
Basic Person Test37.71003.610020.7100
Element Collection Test25.91001.410013.6100
Inheritance Test6.51001.81004.2100
Indexing Test0.0301004.91002.5100
Multithreading Testfailed100failed100failed100
All Tests17.51002.910010.2100

DataNucleus with Derby server has failed in 2 tests (see exceptions).

The results above show that in general ObjectDB embedded is much more efficient than DataNucleus with Derby server in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with Derby database server (10.2) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 9.8 times faster than DataNucleus with Derby server.

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.030) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 3,333 times faster than DataNucleus with Derby server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embedded
Basic Person Test1.11000.851000.99100
Element Collection Test0.811000.621000.71100
Inheritance Test1.21001.31001.2100
Indexing Test1.21001.51001.3100
Graph (Binary Tree) Test0.291000.411000.35100
Multithreading Testfailed100failed100failed100
All Tests0.931000.921000.92100

DataNucleus with Derby server has failed in 2 tests (see exceptions).

The results above show that in general ObjectDB embedded is much more efficient than DataNucleus with Derby server in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with Derby database server (0.92) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 109 times faster than DataNucleus with Derby server.

A huge performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.29) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 345 times faster than DataNucleus with Derby server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embedded
Basic Person Test1.31001.31001.3100
Element Collection Test0.611000.331000.47100
Inheritance Test1.01001.31001.2100
Indexing Test2.31001.91002.1100
Graph (Binary Tree) Test0.261000.461000.36100
Multithreading Testfailed100failed100failed100
All Tests1.11001.11001.1100

DataNucleus with Derby server has failed in 2 tests (see exceptions).

The results above show that in general ObjectDB embedded is much more efficient than DataNucleus with Derby server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby database server (1.1) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 90.9 times faster than DataNucleus with Derby server.

A huge performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.26) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 385 times faster than DataNucleus with Derby server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embedded
Basic Person Test8.71002.91005.8100
Element Collection Test5.71000.721003.2100
Inheritance Test2.41002.61002.5100
Indexing Test1.71003.91002.8100
Graph (Binary Tree) Test0.3597.12.01001.298.5
Multithreading Test3.01006.71004.9100
All Tests3.899.62.81003.399.8

The results above show that in general ObjectDB embedded is much more efficient than DataNucleus with Derby server in performing JPA database operations. Comparing the normalized speed of DataNucleus with Derby database server (3.3) to the normalized speed of ObjectDB embedded database (99.8) reveals that in these tests, ObjectDB embedded is 30.2 times faster than DataNucleus with Derby server.

A huge performance gap has been detected when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.35) to the normalized speed of ObjectDB embedded database (97.1) reveals that in that case, ObjectDB embedded is 277 times faster than DataNucleus with Derby server.

Other Head to Head DBMS/JPA Comparisons