Compare with

Comparison of OpenJPA with H2 server vs DataNucleus with DB4O 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
 OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.70.0592.21.32.90.69
Element Collection Test2.60.0451.51.02.10.52
Inheritance Test4.50.0512.00.853.20.45
Indexing Test7.30.0803.62.35.41.2
Graph (Binary Tree) Test1.1failed0.84failed0.97failed
Multithreading Test7.7failed4.2failed5.9failed
All Tests4.50.0592.41.43.40.71

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.080) to the normalized speed of OpenJPA with H2 database server (7.3) reveals that in that case, OpenJPA with H2 server is 91.2 times faster than DataNucleus with DB4O embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
Basic Person Test2.90.00477.61.85.20.90
Element Collection Test0.00220.00381.91.50.930.77
Inheritance Test0.0130.00354.02.22.01.1
Indexing Test4.10.00438.81.86.50.89
Graph (Binary Tree) Test0.38failed0.49failed0.44failed
Multithreading Test5.9failed14.0failed10.0failed
All Tests2.20.00416.11.84.20.91

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0043) to the normalized speed of OpenJPA with H2 database server (4.1) reveals that in that case, OpenJPA with H2 server is 953 times faster than DataNucleus with DB4O embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.7failed1.0failed2.4failed
Element Collection Test2.0failed1.2failed1.6failed
Inheritance Test2.8failed1.1failed2.0failed
Indexing Test3.8failed7.5failed5.7failed
Multithreading Test0.98failed1.0failed1.0failed
All Tests2.7failed2.4failed2.5failed

DataNucleus with DB4O embedded has failed in 10 tests (see exceptions).

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.00.0122.00.762.50.39
Element Collection Test0.00780.0121.91.10.940.53
Inheritance Test0.0340.0112.80.811.40.41
Indexing Test2.80.0113.21.33.00.64
Graph (Binary Tree) Test0.79failed0.43failed0.61failed
Multithreading Test7.0failed2.5failed4.8failed
All Tests2.30.0122.10.972.20.49

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.011) to the normalized speed of OpenJPA with H2 database server (2.8) reveals that in that case, OpenJPA with H2 server is 255 times faster than DataNucleus with DB4O embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.20.0112.21.52.70.74
Element Collection Test0.00600.0100.881.60.440.80
Inheritance Test0.0300.00933.11.11.60.57
Indexing Test6.50.0173.62.15.11.1
Graph (Binary Tree) Test0.73failed0.75failed0.74failed
Multithreading Test7.6failed5.2failed6.4failed
All Tests3.00.0122.61.62.80.79

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.017) to the normalized speed of OpenJPA with H2 database server (6.5) reveals that in that case, OpenJPA with H2 server is 382 times faster than DataNucleus with DB4O embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
OpenJPA
H2 server
DataNucleus
DB4O embedded
Basic Person Test3.30.0223.01.33.10.68
Element Collection Test0.930.0181.51.31.20.66
Inheritance Test1.50.0192.61.22.00.63
Indexing Test4.90.0285.41.95.10.94
Graph (Binary Tree) Test0.75failed0.63failed0.69failed
Multithreading Test5.9failed5.4failed5.6failed
All Tests2.90.0223.21.43.00.73

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

A huge performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.028) to the normalized speed of OpenJPA with H2 database server (4.9) reveals that in that case, OpenJPA with H2 server is 175 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons