Compare with

Comparison of DataNucleus with H2 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
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embedded
Basic Person Test3.41002.21002.8100
Element Collection Test1.21000.641000.92100
Inheritance Test3.01001.91002.4100
Indexing Test5.31003.51004.4100
Graph (Binary Tree) Test2.188.41.31001.794.2
Multithreading Test10.01004.31007.2100
All Tests4.298.12.31003.299.0

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

A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (0.64) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 156 times faster than DataNucleus with H2 server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embedded
Basic Person Test2.51005.21003.9100
Element Collection Test0.561001.11000.82100
Inheritance Test2.21006.11004.2100
Indexing Test2.11007.71004.9100
Graph (Binary Tree) Test5.71008.91007.3100
Multithreading Test2.31008.71005.5100
All Tests2.51006.31004.4100

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embedded
Basic Person Test4.11001.31002.7100
Element Collection Test4.01000.491002.3100
Inheritance Test2.91001.51002.2100
Indexing Test0.00361001.51000.75100
Multithreading Test1.3100failed1001.3100
All Tests2.51001.21001.9100

DataNucleus with H2 server has failed in 1 tests (see exceptions).

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embedded
Basic Person Test2.51001.41001.9100
Element Collection Test2.01001.01001.5100
Inheritance Test2.41002.31002.3100
Indexing Test2.71003.01002.9100
Graph (Binary Tree) Test1.81000.601001.2100
Multithreading Testfailed100failed100failed100
All Tests2.31001.71002.0100

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

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embedded
Basic Person Test3.41001.31002.3100
Element Collection Test1.51000.681001.1100
Inheritance Test2.71001.31002.0100
Indexing Test5.71001.91003.8100
Graph (Binary Tree) Test1.51001.21001.3100
Multithreading Testfailed1005.11005.1100
All Tests3.01001.91002.4100

DataNucleus with H2 server has failed in 1 tests (see exceptions).

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

A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (0.68) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 147 times faster than DataNucleus with H2 server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embedded
Basic Person Test3.21002.31002.7100
Element Collection Test1.91000.781001.3100
Inheritance Test2.61002.61002.6100
Indexing Test3.21003.51003.3100
Graph (Binary Tree) Test2.897.13.01002.998.5
Multithreading Test4.51006.01005.3100
All Tests2.999.62.81002.999.8

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

A huge performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (0.78) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 128 times faster than DataNucleus with H2 server.

Other Head to Head DBMS/JPA Comparisons