Compare with

Comparison of ObjectDB embedded vs DataNucleus with H2 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
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
Basic Person Test1003.41002.21002.8
Element Collection Test1001.21000.641000.92
Inheritance Test1003.01001.91002.4
Indexing Test1005.31003.51004.4
Graph (Binary Tree) Test88.42.11001.394.21.7
Multithreading Test10010.01004.31007.2
All Tests98.14.21002.399.03.2

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
 ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
Basic Person Test1002.51005.21003.9
Element Collection Test1000.561001.11000.82
Inheritance Test1002.21006.11004.2
Indexing Test1002.11007.71004.9
Graph (Binary Tree) Test1005.71008.91007.3
Multithreading Test1002.31008.71005.5
All Tests1002.51006.31004.4

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
 ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
Basic Person Test1004.11001.31002.7
Element Collection Test1004.01000.491002.3
Inheritance Test1002.91001.51002.2
Indexing Test1000.00361001.51000.75
Multithreading Test1001.3100failed1001.3
All Tests1002.51001.21001.9

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
 ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
Basic Person Test1002.51001.41001.9
Element Collection Test1002.01001.01001.5
Inheritance Test1002.41002.31002.3
Indexing Test1002.71003.01002.9
Graph (Binary Tree) Test1001.81000.601001.2
Multithreading Test100failed100failed100failed
All Tests1002.31001.71002.0

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
 ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
Basic Person Test1003.41001.31002.3
Element Collection Test1001.51000.681001.1
Inheritance Test1002.71001.31002.0
Indexing Test1005.71001.91003.8
Graph (Binary Tree) Test1001.51001.21001.3
Multithreading Test100failed1005.11005.1
All Tests1003.01001.91002.4

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
 ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
ObjectDB embeddedDataNucleus
H2 server
Basic Person Test1003.21002.31002.7
Element Collection Test1001.91000.781001.3
Inheritance Test1002.61002.61002.6
Indexing Test1003.21003.51003.3
Graph (Binary Tree) Test97.12.81003.098.52.9
Multithreading Test1004.51006.01005.3
All Tests99.62.91002.899.82.9

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