Compare with

Comparison of EclipseLink with H2 embedded 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
 EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
Basic Person Test25.14.68.92.817.03.7
Element Collection Test20.42.48.01.614.22.0
Inheritance Test28.74.68.72.718.73.7
Indexing Test37.67.614.04.825.86.2
Graph (Binary Tree) Test17.71.614.71.416.21.5
Multithreading Test30.38.611.43.320.85.9
All Tests26.64.910.92.818.83.8

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
Basic Person Test30.46.829.114.929.710.9
Element Collection Test19.65.427.67.623.66.5
Inheritance Test33.88.839.814.836.811.8
Indexing Test22.29.241.314.131.811.6
Graph (Binary Tree) Test16.09.920.015.818.012.9
Multithreading Test33.711.929.011.531.411.7
All Tests25.98.731.113.128.510.9

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
Basic Person Test4.439.11.47.52.923.3
Element Collection Test4.146.02.46.73.226.3
Inheritance Test3.47.72.03.82.75.7
Indexing Test13.00.05322.88.017.94.0
Multithreading Test1.0failed0.67failed0.85failed
All Tests5.223.25.96.55.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 more efficient than EclipseLink with H2 embedded in executing the tested JPA queries. Comparing the normalized speed of EclipseLink with H2 embedded database (5.5) to the normalized speed of DataNucleus with Derby embedded database (14.8) reveals that in these tests, DataNucleus with Derby embedded is 2.7 times faster than EclipseLink with H2 embedded.

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

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 EclipseLink with H2 embedded database (13.0) reveals that in that case, DataNucleus with Derby embedded is 245 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 embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
Basic Person Test16.64.07.63.812.13.9
Element Collection Test15.33.710.54.512.94.1
Inheritance Test15.74.49.84.812.74.6
Indexing Test12.15.29.94.211.04.7
Graph (Binary Tree) Test13.72.77.01.510.32.1
Multithreading Test20.9failed4.2failed12.6failed
All Tests15.74.08.23.712.03.9

DataNucleus with Derby embedded 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 embedded in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with Derby embedded database (3.9) to the normalized speed of EclipseLink with H2 embedded database (12.0) reveals that in these tests, EclipseLink with H2 embedded is 3.1 times faster than DataNucleus with Derby embedded.

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
Basic Person Test35.13.519.61.327.42.4
Element Collection Test19.31.98.51.613.91.7
Inheritance Test36.02.414.01.325.01.9
Indexing Test42.56.619.21.930.94.3
Graph (Binary Tree) Test12.20.8114.40.9313.30.87
Multithreading Test54.4failed25.8failed40.1failed
All Tests33.33.016.91.425.12.2

DataNucleus with Derby embedded 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 embedded in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby embedded database (2.2) to the normalized speed of EclipseLink with H2 embedded database (25.1) reveals that in these tests, EclipseLink with H2 embedded is 11.4 times faster than DataNucleus with Derby embedded.

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

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
Basic Person Test36.253.339.253.337.753.3
Element Collection Test33.342.634.942.634.142.6
Inheritance Test35.448.136.248.135.848.1
Indexing Test39.862.343.763.341.762.8
Graph (Binary Tree) Test41.013.628.410.234.711.9
Multithreading Test48.752.012.48.030.630.0
All Tests39.145.332.537.635.841.5

The results above show that in general DataNucleus with Derby embedded is slightly more efficient than EclipseLink with H2 embedded in using disk space.

On the other hand, DataNucleus with Derby embedded is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized score of DataNucleus with Derby embedded database (13.6) to the normalized score of EclipseLink with H2 embedded database (41.0) reveals that in that case, DataNucleus with Derby embedded is 3.0 times less efficient than EclipseLink with H2 embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
Basic Person Test22.311.613.36.117.88.8
Element Collection Test15.711.911.44.413.68.1
Inheritance Test23.55.614.95.519.25.5
Indexing Test25.55.721.56.623.56.2
Graph (Binary Tree) Test14.93.714.04.914.54.3
Multithreading Test28.110.314.27.421.18.8
All Tests21.98.014.95.718.46.9

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

A large performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (5.7) to the normalized speed of EclipseLink with H2 embedded database (25.5) reveals that in that case, EclipseLink with H2 embedded is 4.5 times faster than DataNucleus with Derby embedded.

Other Head to Head DBMS/JPA Comparisons