Compare with

Comparison of DataNucleus with H2 server vs EclipseLink with Derby 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
 DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
Basic Person Test3.43.82.23.12.83.4
Element Collection Test1.22.20.641.50.921.8
Inheritance Test3.03.91.92.92.43.4
Indexing Test5.35.23.54.34.44.7
Graph (Binary Tree) Test2.11.91.31.71.71.8
Multithreading Test10.06.14.33.97.25.0
All Tests4.23.82.32.93.23.4

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

A large 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 EclipseLink with Derby database server (1.5) reveals that in that case, EclipseLink with Derby server is 2.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
 DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
Basic Person Test2.56.45.211.33.98.8
Element Collection Test0.561.81.12.40.822.1
Inheritance Test2.23.76.112.94.28.3
Indexing Test2.13.67.712.84.98.2
Graph (Binary Tree) Test5.70.618.90.737.30.67
Multithreading Test2.38.58.719.85.514.1
All Tests2.54.16.310.04.47.0

The results above show that in general EclipseLink with Derby server is more efficient than DataNucleus with H2 server in retrieving JPA entity objects from the database.

A large performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (2.3) to the normalized speed of EclipseLink with Derby database server (8.5) reveals that in that case, EclipseLink with Derby server is 3.7 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with Derby server is slower, for instance, when using graphs of objects with large retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (0.73) to the normalized speed of DataNucleus with H2 database server (8.9) reveals that in that case, EclipseLink with Derby server is 12.2 times slower than DataNucleus with H2 server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
Basic Person Test4.145.81.35.32.725.6
Element Collection Test4.035.20.490.992.318.1
Inheritance Test2.923.11.55.92.214.5
Indexing Test0.00362.51.512.20.757.4
Multithreading Test1.334.3failed7.71.321.0
All Tests2.528.21.26.41.917.3

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

The results above show that in general EclipseLink with Derby 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 EclipseLink with Derby database server (17.3) reveals that in these tests, EclipseLink with Derby server is 9.1 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 EclipseLink with Derby database server (2.5) reveals that in that case, EclipseLink with Derby server is 694 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
 DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
Basic Person Test2.53.91.44.41.94.1
Element Collection Test2.01.71.01.61.51.6
Inheritance Test2.44.62.36.12.35.3
Indexing Test2.74.53.07.62.96.1
Graph (Binary Tree) Test1.80.700.600.421.20.56
Multithreading Testfailed7.3failed4.8failed6.0
All Tests2.33.81.74.22.04.0

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

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

A large performance gap has been detected when using simple basic entities with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (1.4) to the normalized speed of EclipseLink with Derby database server (4.4) reveals that in that case, EclipseLink with Derby server is 3.1 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with Derby server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of EclipseLink with Derby database server (0.70) to the normalized speed of DataNucleus with H2 database server (1.8) reveals that in that case, EclipseLink with Derby server is 2.6 times slower than DataNucleus with H2 server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
Basic Person Test3.42.81.33.92.33.3
Element Collection Test1.51.20.680.551.10.87
Inheritance Test2.73.31.33.72.03.5
Indexing Test5.74.91.93.53.84.2
Graph (Binary Tree) Test1.50.511.20.501.30.51
Multithreading Testfailed4.85.15.75.15.3
All Tests3.02.91.93.02.43.0

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

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

A large performance gap has been detected when using simple basic entities with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (1.3) to the normalized speed of EclipseLink with Derby database server (3.9) reveals that in that case, EclipseLink with Derby server is 3.0 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with Derby server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of EclipseLink with Derby database server (0.51) to the normalized speed of DataNucleus with H2 database server (1.5) reveals that in that case, EclipseLink with Derby server is 2.9 times slower than DataNucleus with H2 server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
DataNucleus
H2 server
EclipseLink
Derby server
Basic Person Test3.212.52.35.62.79.1
Element Collection Test1.98.40.781.41.34.9
Inheritance Test2.67.72.66.32.67.0
Indexing Test3.24.13.58.13.36.1
Graph (Binary Tree) Test2.80.933.00.832.90.88
Multithreading Test4.512.26.08.45.310.3
All Tests2.97.92.85.22.96.6

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

A large performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (1.9) to the normalized speed of EclipseLink with Derby database server (8.4) reveals that in that case, EclipseLink with Derby server is 4.4 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with Derby server is slower, for instance, when using graphs of objects with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (0.83) to the normalized speed of DataNucleus with H2 database server (3.0) reveals that in that case, EclipseLink with Derby server is 3.6 times slower than DataNucleus with H2 server.

Other Head to Head DBMS/JPA Comparisons