Compare with

Comparison of EclipseLink with H2 embedded vs DataNucleus 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
 EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
Basic Person Test25.12.88.92.317.02.6
Element Collection Test20.40.718.00.3514.20.53
Inheritance Test28.72.78.72.018.72.3
Indexing Test37.64.514.04.025.84.3
Graph (Binary Tree) Test17.70.6214.70.5316.20.57
Multithreading Test30.34.911.43.420.84.1
All Tests26.62.710.92.118.82.4

The results above show that in general EclipseLink with H2 embedded is much more efficient than DataNucleus with Derby server in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with Derby database server (2.4) to the normalized speed of EclipseLink with H2 embedded database (18.8) reveals that in these tests, EclipseLink with H2 embedded is 7.8 times faster than DataNucleus with Derby server.

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
Basic Person Test30.40.5629.16.329.73.4
Element Collection Test19.60.3627.60.9323.60.64
Inheritance Test33.80.4539.86.836.83.6
Indexing Test22.20.5041.37.131.83.8
Graph (Binary Tree) Test16.00.2220.06.618.03.4
Multithreading Test33.71.229.010.031.45.6
All Tests25.90.5531.16.328.53.4

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

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.45) to the normalized speed of EclipseLink with H2 embedded database (33.8) reveals that in that case, EclipseLink with H2 embedded is 75.1 times faster than DataNucleus with Derby server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
Basic Person Test4.437.71.43.62.920.7
Element Collection Test4.125.92.41.43.213.6
Inheritance Test3.46.52.01.82.74.2
Indexing Test13.00.03022.84.917.92.5
Multithreading Test1.0failed0.67failed0.85failed
All Tests5.217.55.92.95.510.2

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

The results above show that in general DataNucleus with Derby server is more efficient than EclipseLink with H2 embedded in executing the tested JPA queries.

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
Basic Person Test16.61.17.60.8512.10.99
Element Collection Test15.30.8110.50.6212.90.71
Inheritance Test15.71.29.81.312.71.2
Indexing Test12.11.29.91.511.01.3
Graph (Binary Tree) Test13.70.297.00.4110.30.35
Multithreading Test20.9failed4.2failed12.6failed
All Tests15.70.938.20.9212.00.92

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

The results above show that in general EclipseLink with H2 embedded is much more efficient than DataNucleus with Derby server in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with Derby database server (0.92) to the normalized speed of EclipseLink with H2 embedded database (12.0) reveals that in these tests, EclipseLink with H2 embedded is 13.0 times faster than DataNucleus with Derby server.

A huge performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.29) to the normalized speed of EclipseLink with H2 embedded database (13.7) reveals that in that case, EclipseLink with H2 embedded is 47.2 times faster than DataNucleus with Derby server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
Basic Person Test35.11.319.61.327.41.3
Element Collection Test19.30.618.50.3313.90.47
Inheritance Test36.01.014.01.325.01.2
Indexing Test42.52.319.21.930.92.1
Graph (Binary Tree) Test12.20.2614.40.4613.30.36
Multithreading Test54.4failed25.8failed40.1failed
All Tests33.31.116.91.125.11.1

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

The results above show that in general EclipseLink with H2 embedded is much more efficient than DataNucleus with Derby server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby database server (1.1) to the normalized speed of EclipseLink with H2 embedded database (25.1) reveals that in these tests, EclipseLink with H2 embedded is 22.8 times faster than DataNucleus with Derby server.

A huge performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.26) to the normalized speed of EclipseLink with H2 embedded database (12.2) reveals that in that case, EclipseLink with H2 embedded is 46.9 times faster than DataNucleus with Derby server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
EclipseLink
H2 embedded
DataNucleus
Derby server
Basic Person Test22.38.713.32.917.85.8
Element Collection Test15.75.711.40.7213.63.2
Inheritance Test23.52.414.92.619.22.5
Indexing Test25.51.721.53.923.52.8
Graph (Binary Tree) Test14.90.3514.02.014.51.2
Multithreading Test28.13.014.26.721.14.9
All Tests21.93.814.92.818.43.3

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

A huge performance gap has been detected when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.35) to the normalized speed of EclipseLink with H2 embedded database (14.9) reveals that in that case, EclipseLink with H2 embedded is 42.6 times faster than DataNucleus with Derby server.

Other Head to Head DBMS/JPA Comparisons