Compare with

Comparison of ObjectDB embedded vs DataNucleus with Derby server

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
 ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
Basic Person Test1002.81002.31002.6
Element Collection Test1000.711000.351000.53
Inheritance Test1002.71002.01002.3
Indexing Test1004.51004.01004.3
Graph (Binary Tree) Test88.40.621000.5394.20.57
Multithreading Test1004.91003.41004.1
All Tests98.12.71002.199.02.4

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
 ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
Basic Person Test1000.561006.31003.4
Element Collection Test1000.361000.931000.64
Inheritance Test1000.451006.81003.6
Indexing Test1000.501007.11003.8
Graph (Binary Tree) Test1000.221006.61003.4
Multithreading Test1001.210010.01005.6
All Tests1000.551006.31003.4

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
 ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
Basic Person Test10037.71003.610020.7
Element Collection Test10025.91001.410013.6
Inheritance Test1006.51001.81004.2
Indexing Test1000.0301004.91002.5
Multithreading Test100failed100failed100failed
All Tests10017.51002.910010.2

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
 ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
Basic Person Test1001.11000.851000.99
Element Collection Test1000.811000.621000.71
Inheritance Test1001.21001.31001.2
Indexing Test1001.21001.51001.3
Graph (Binary Tree) Test1000.291000.411000.35
Multithreading Test100failed100failed100failed
All Tests1000.931000.921000.92

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
 ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
Basic Person Test1001.31001.31001.3
Element Collection Test1000.611000.331000.47
Inheritance Test1001.01001.31001.2
Indexing Test1002.31001.91002.1
Graph (Binary Tree) Test1000.261000.461000.36
Multithreading Test100failed100failed100failed
All Tests1001.11001.11001.1

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
 ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
ObjectDB embeddedDataNucleus
Derby server
Basic Person Test1008.71002.91005.8
Element Collection Test1005.71000.721003.2
Inheritance Test1002.41002.61002.5
Indexing Test1001.71003.91002.8
Graph (Binary Tree) Test97.10.351002.098.51.2
Multithreading Test1003.01006.71004.9
All Tests99.63.81002.899.83.3

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