Compare with

Comparison of ObjectDB embedded vs DataNucleus with Derby 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
 ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
Basic Person Test1004.61002.81003.7
Element Collection Test1002.41001.61002.0
Inheritance Test1004.61002.71003.7
Indexing Test1007.61004.81006.2
Graph (Binary Tree) Test88.41.61001.494.21.5
Multithreading Test1008.61003.31005.9
All Tests98.14.91002.899.03.8

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
Basic Person Test1006.810014.910010.9
Element Collection Test1005.41007.61006.5
Inheritance Test1008.810014.810011.8
Indexing Test1009.210014.110011.6
Graph (Binary Tree) Test1009.910015.810012.9
Multithreading Test10011.910011.510011.7
All Tests1008.710013.110010.9

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

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (5.4) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 18.5 times faster than DataNucleus with Derby embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
Basic Person Test10039.11007.510023.3
Element Collection Test10046.01006.710026.3
Inheritance Test1007.71003.81005.7
Indexing Test1000.0531008.01004.0
Multithreading Test100failed100failed100failed
All Tests10023.21006.510014.8

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

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
Basic Person Test1004.01003.81003.9
Element Collection Test1003.71004.51004.1
Inheritance Test1004.41004.81004.6
Indexing Test1005.21004.21004.7
Graph (Binary Tree) Test1002.71001.51002.1
Multithreading Test100failed100failed100failed
All Tests1004.01003.71003.9

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

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
Basic Person Test1003.51001.31002.4
Element Collection Test1001.91001.61001.7
Inheritance Test1002.41001.31001.9
Indexing Test1006.61001.91004.3
Graph (Binary Tree) Test1000.811000.931000.87
Multithreading Test100failed100failed100failed
All Tests1003.01001.41002.2

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

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
Basic Person Test10053.310053.310053.3
Element Collection Test10042.610042.610042.6
Inheritance Test10048.110048.110048.1
Indexing Test10062.310063.310062.8
Graph (Binary Tree) Test10013.610010.210011.9
Multithreading Test91.152.022.08.056.630.0
All Tests98.545.387.037.692.841.5

The results above show that in general ObjectDB embedded is more efficient than DataNucleus with Derby embedded in using disk space. Comparing the normalized score of DataNucleus with Derby embedded database (41.5) to the normalized score of ObjectDB embedded database (92.8) reveals that in these tests, ObjectDB embedded is 2.2 times more efficient than DataNucleus with Derby embedded.

A large gap has been detected when using graphs of objects with large transaction size. Comparing the normalized score of DataNucleus with Derby embedded database (10.2) to the normalized score of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 9.8 times more efficient than DataNucleus with Derby embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
Basic Person Test10011.61006.11008.8
Element Collection Test10011.91004.41008.1
Inheritance Test1005.61005.51005.5
Indexing Test1005.71006.61006.2
Graph (Binary Tree) Test97.13.71004.998.54.3
Multithreading Test10010.31007.41008.8
All Tests99.68.01005.799.86.9

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

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 embedded database (3.7) to the normalized speed of ObjectDB embedded database (97.1) reveals that in that case, ObjectDB embedded is 26.2 times faster than DataNucleus with Derby embedded.

Other Head to Head DBMS/JPA Comparisons