Compare with

Comparison of OpenJPA with Derby 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
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
Basic Person Test3.10.0592.71.32.90.69
Element Collection Test2.00.0451.71.01.80.52
Inheritance Test3.00.0512.30.852.60.45
Indexing Test4.70.0804.12.34.41.2
Graph (Binary Tree) Test0.71failed0.64failed0.67failed
Multithreading Test6.0failed3.8failed4.9failed
All Tests3.30.0592.51.42.90.71

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

The results above show that in general OpenJPA with Derby 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 Derby database server (2.9) reveals that in these tests, OpenJPA with Derby server is 4.1 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.051) to the normalized speed of OpenJPA with Derby database server (3.0) reveals that in that case, OpenJPA with Derby server is 58.8 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
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
Basic Person Test0.780.004711.61.86.20.90
Element Collection Test0.00240.00381.11.50.540.77
Inheritance Test0.0140.00355.02.22.51.1
Indexing Test0.620.004313.01.86.80.89
Graph (Binary Tree) Test0.065failed0.39failed0.23failed
Multithreading Test1.6failed19.0failed10.3failed
All Tests0.510.00418.41.84.40.91

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

The results above show that in general OpenJPA with Derby 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 Derby database server (4.4) reveals that in these tests, OpenJPA with Derby server is 4.8 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using simple basic entities with small retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0047) to the normalized speed of OpenJPA with Derby database server (0.78) reveals that in that case, OpenJPA with Derby server is 166 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
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
Basic Person Test29.2failed5.5failed17.3failed
Element Collection Test2.2failed1.4failed1.8failed
Inheritance Test2.2failed1.0failed1.6failed
Indexing Test2.2failed11.7failed7.0failed
Multithreading Test35.5failed8.3failed21.9failed
All Tests14.3failed5.6failed9.9failed

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
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
Basic Person Test1.50.0124.00.762.80.39
Element Collection Test0.00810.0121.91.10.940.53
Inheritance Test0.0430.0113.80.811.90.41
Indexing Test1.80.0116.81.34.30.64
Graph (Binary Tree) Test0.16failed0.27failed0.22failed
Multithreading Test6.9failed5.0failed5.9failed
All Tests1.70.0123.60.972.70.49

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

The results above show that in general OpenJPA with Derby 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 Derby database server (2.7) reveals that in these tests, OpenJPA with Derby server is 5.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 Derby database server (1.8) reveals that in that case, OpenJPA with Derby server is 164 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
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
Basic Person Test1.40.0113.71.52.50.74
Element Collection Test0.00820.0101.41.60.710.80
Inheritance Test0.0350.00932.51.11.30.57
Indexing Test2.30.0173.52.12.91.1
Graph (Binary Tree) Test0.13failed0.35failed0.24failed
Multithreading Test3.6failed4.0failed3.8failed
All Tests1.30.0122.61.61.90.79

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

The results above show that in general OpenJPA with Derby server is 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 Derby database server (1.9) reveals that in these tests, OpenJPA with Derby server is 2.4 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 Derby database server (2.3) reveals that in that case, OpenJPA with Derby server is 135 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
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
OpenJPA
Derby server
DataNucleus
DB4O embedded
Basic Person Test7.20.0225.51.36.40.68
Element Collection Test0.840.0181.51.31.20.66
Inheritance Test1.10.0192.91.22.00.63
Indexing Test2.30.0287.81.95.10.94
Graph (Binary Tree) Test0.27failed0.41failed0.34failed
Multithreading Test10.7failed8.0failed9.4failed
All Tests3.90.0224.51.44.20.73

The results above show that in general OpenJPA with Derby 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 Derby database server (4.2) reveals that in these tests, OpenJPA with Derby server is 5.8 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using simple basic entities with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.022) to the normalized speed of OpenJPA with Derby database server (7.2) reveals that in that case, OpenJPA with Derby server is 327 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons