Compare with

Comparison of OpenJPA with H2 server vs DataNucleus with Derby 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
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
Basic Person Test3.74.62.22.82.93.7
Element Collection Test2.62.41.51.62.12.0
Inheritance Test4.54.62.02.73.23.7
Indexing Test7.37.63.64.85.46.2
Graph (Binary Tree) Test1.11.60.841.40.971.5
Multithreading Test7.78.64.23.35.95.9
All Tests4.54.92.42.83.43.8

The results above show that in general DataNucleus with Derby embedded is slightly more efficient than OpenJPA with H2 server in persisting JPA entity objects to the database.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
Basic Person Test2.96.87.614.95.210.9
Element Collection Test0.00225.41.97.60.936.5
Inheritance Test0.0138.84.014.82.011.8
Indexing Test4.19.28.814.16.511.6
Graph (Binary Tree) Test0.389.90.4915.80.4412.9
Multithreading Test5.911.914.011.510.011.7
All Tests2.28.76.113.14.210.9

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

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with H2 database server (0.0022) to the normalized speed of DataNucleus with Derby embedded database (5.4) reveals that in that case, DataNucleus with Derby embedded is 2,455 times faster than OpenJPA with H2 server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
Basic Person Test3.739.11.07.52.423.3
Element Collection Test2.046.01.26.71.626.3
Inheritance Test2.87.71.13.82.05.7
Indexing Test3.80.0537.58.05.74.0
Multithreading Test0.98failed1.0failed1.0failed
All Tests2.723.22.46.52.514.8

DataNucleus with Derby embedded has failed in 2 tests (see exceptions).

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

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

On the other hand, DataNucleus with Derby embedded is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (0.053) to the normalized speed of OpenJPA with H2 database server (3.8) reveals that in that case, DataNucleus with Derby embedded is 71.7 times slower than OpenJPA with H2 server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
Basic Person Test3.04.02.03.82.53.9
Element Collection Test0.00783.71.94.50.944.1
Inheritance Test0.0344.42.84.81.44.6
Indexing Test2.85.23.24.23.04.7
Graph (Binary Tree) Test0.792.70.431.50.612.1
Multithreading Test7.0failed2.5failed4.8failed
All Tests2.34.02.13.72.23.9

DataNucleus with Derby embedded has failed in 2 tests (see exceptions).

The results above show that in general DataNucleus with Derby embedded is more efficient than OpenJPA with H2 server in updating JPA entity objects in the database.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with H2 database server (0.0078) to the normalized speed of DataNucleus with Derby embedded database (3.7) reveals that in that case, DataNucleus with Derby embedded is 474 times faster than OpenJPA with H2 server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
Basic Person Test3.23.52.21.32.72.4
Element Collection Test0.00601.90.881.60.441.7
Inheritance Test0.0302.43.11.31.61.9
Indexing Test6.56.63.61.95.14.3
Graph (Binary Tree) Test0.730.810.750.930.740.87
Multithreading Test7.6failed5.2failed6.4failed
All Tests3.03.02.61.42.82.2

DataNucleus with Derby embedded has failed in 2 tests (see exceptions).

The results above show that in general OpenJPA with H2 server is slightly more efficient than DataNucleus with Derby embedded in deleting JPA entity objects from the database.

A large performance gap has been detected when using class inheritance in the object model with large transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (1.3) to the normalized speed of OpenJPA with H2 database server (3.1) reveals that in that case, OpenJPA with H2 server is 2.4 times faster than DataNucleus with Derby embedded.

On the other hand, OpenJPA with H2 server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with H2 database server (0.0060) to the normalized speed of DataNucleus with Derby embedded database (1.9) reveals that in that case, OpenJPA with H2 server is 317 times slower than DataNucleus with Derby embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
OpenJPA
H2 server
DataNucleus
Derby embedded
Basic Person Test3.311.63.06.13.18.8
Element Collection Test0.9311.91.54.41.28.1
Inheritance Test1.55.62.65.52.05.5
Indexing Test4.95.75.46.65.16.2
Graph (Binary Tree) Test0.753.70.634.90.694.3
Multithreading Test5.910.35.47.45.68.8
All Tests2.98.03.25.73.06.9

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

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with H2 database server (0.93) to the normalized speed of DataNucleus with Derby embedded database (11.9) reveals that in that case, DataNucleus with Derby embedded is 12.8 times faster than OpenJPA with H2 server.

Other Head to Head DBMS/JPA Comparisons