Compare with

Comparison of ObjectDB server 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 serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
Basic Person Test35.23.474.12.254.72.8
Element Collection Test38.21.257.80.6448.00.92
Inheritance Test32.73.072.81.952.72.4
Indexing Test49.95.390.13.570.04.4
Graph (Binary Tree) Test1002.189.21.394.61.7
Multithreading Test76.610.099.44.388.07.2
All Tests55.44.280.62.368.03.2

The results above show that in general ObjectDB server 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 database server (68.0) reveals that in these tests, ObjectDB server is 21.2 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 database server (57.8) reveals that in that case, ObjectDB server is 90.3 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 serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
Basic Person Test15.72.545.45.230.53.9
Element Collection Test19.90.5649.21.134.60.82
Inheritance Test13.22.249.46.131.34.2
Indexing Test14.02.159.57.736.84.9
Graph (Binary Tree) Test19.95.724.78.922.37.3
Multithreading Test19.72.360.28.740.05.5
All Tests17.12.548.16.332.64.4

The results above show that in general ObjectDB server 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 database server (32.6) reveals that in these tests, ObjectDB server is 7.4 times faster than DataNucleus with H2 server.

A huge performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (1.1) to the normalized speed of ObjectDB database server (49.2) reveals that in that case, ObjectDB server is 44.7 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 serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
Basic Person Test38.84.125.91.332.42.7
Element Collection Test39.54.033.10.4936.32.3
Inheritance Test34.82.934.01.534.42.2
Indexing Test14.50.003653.31.533.90.75
Multithreading Test50.81.352.1failed51.51.3
All Tests35.72.539.71.237.71.9

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

The results above show that in general ObjectDB server 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 database server (37.7) reveals that in these tests, ObjectDB server is 19.8 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 database server (14.5) reveals that in that case, ObjectDB server is 4,028 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 serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
Basic Person Test18.32.540.91.429.61.9
Element Collection Test21.12.053.71.037.41.5
Inheritance Test19.92.451.92.335.92.3
Indexing Test17.92.752.13.035.02.9
Graph (Binary Tree) Test42.61.824.10.6033.31.2
Multithreading Test68.6failed68.7failed68.6failed
All Tests31.42.348.61.740.02.0

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

The results above show that in general ObjectDB server 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 database server (40.0) reveals that in these tests, ObjectDB server is 20.0 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 (1.0) to the normalized speed of ObjectDB database server (53.7) reveals that in that case, ObjectDB server is 53.7 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 serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
Basic Person Test20.23.467.71.344.02.3
Element Collection Test22.91.557.60.6840.21.1
Inheritance Test23.12.761.61.342.32.0
Indexing Test34.95.755.91.945.43.8
Graph (Binary Tree) Test19.31.527.91.223.61.3
Multithreading Test38.5failed50.55.144.55.1
All Tests26.53.053.51.940.02.4

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

The results above show that in general ObjectDB server 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 database server (40.0) reveals that in these tests, ObjectDB server is 16.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 database server (57.6) reveals that in that case, ObjectDB server is 84.7 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 serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
ObjectDB serverDataNucleus
H2 server
Basic Person Test25.63.250.82.338.22.7
Element Collection Test28.31.950.30.7839.31.3
Inheritance Test24.72.653.92.639.32.6
Indexing Test26.23.262.23.544.23.3
Graph (Binary Tree) Test45.42.841.53.043.52.9
Multithreading Test50.84.566.26.058.55.3
All Tests33.12.954.62.843.92.9

The results above show that in general ObjectDB server 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 database server (43.9) reveals that in these tests, ObjectDB server is 15.1 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 database server (50.3) reveals that in that case, ObjectDB server is 64.5 times faster than DataNucleus with H2 server.

Other Head to Head DBMS/JPA Comparisons