Compare with

Comparison of DataNucleus with Derby embedded 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 embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embedded
Basic Person Test4.61002.81003.7100
Element Collection Test2.41001.61002.0100
Inheritance Test4.61002.71003.7100
Indexing Test7.61004.81006.2100
Graph (Binary Tree) Test1.688.41.41001.594.2
Multithreading Test8.61003.31005.9100
All Tests4.998.12.81003.899.0

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
 DataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embedded
Basic Person Test6.810014.910010.9100
Element Collection Test5.41007.61006.5100
Inheritance Test8.810014.810011.8100
Indexing Test9.210014.110011.6100
Graph (Binary Tree) Test9.910015.810012.9100
Multithreading Test11.910011.510011.7100
All Tests8.710013.110010.9100

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
 DataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embedded
Basic Person Test39.11007.510023.3100
Element Collection Test46.01006.710026.3100
Inheritance Test7.71003.81005.7100
Indexing Test0.0531008.01004.0100
Multithreading Testfailed100failed100failed100
All Tests23.21006.510014.8100

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
 DataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embedded
Basic Person Test4.01003.81003.9100
Element Collection Test3.71004.51004.1100
Inheritance Test4.41004.81004.6100
Indexing Test5.21004.21004.7100
Graph (Binary Tree) Test2.71001.51002.1100
Multithreading Testfailed100failed100failed100
All Tests4.01003.71003.9100

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
 DataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embedded
Basic Person Test3.51001.31002.4100
Element Collection Test1.91001.61001.7100
Inheritance Test2.41001.31001.9100
Indexing Test6.61001.91004.3100
Graph (Binary Tree) Test0.811000.931000.87100
Multithreading Testfailed100failed100failed100
All Tests3.01001.41002.2100

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
 DataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embedded
Basic Person Test53.310053.310053.3100
Element Collection Test42.610042.610042.6100
Inheritance Test48.110048.110048.1100
Indexing Test62.310063.310062.8100
Graph (Binary Tree) Test13.610010.210011.9100
Multithreading Test52.091.18.022.030.056.6
All Tests45.398.537.687.041.592.8

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
 DataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embeddedDataNucleus
Derby embedded
ObjectDB embedded
Basic Person Test11.61006.11008.8100
Element Collection Test11.91004.41008.1100
Inheritance Test5.61005.51005.5100
Indexing Test5.71006.61006.2100
Graph (Binary Tree) Test3.797.14.91004.398.5
Multithreading Test10.31007.41008.8100
All Tests8.099.65.71006.999.8

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