Compare with

Comparison of DataNucleus with Derby embedded vs EclipseLink with H2 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
 DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
Basic Person Test4.625.12.88.93.717.0
Element Collection Test2.420.41.68.02.014.2
Inheritance Test4.628.72.78.73.718.7
Indexing Test7.637.64.814.06.225.8
Graph (Binary Tree) Test1.617.71.414.71.516.2
Multithreading Test8.630.33.311.45.920.8
All Tests4.926.62.810.93.818.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
 DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
Basic Person Test6.830.414.929.110.929.7
Element Collection Test5.419.67.627.66.523.6
Inheritance Test8.833.814.839.811.836.8
Indexing Test9.222.214.141.311.631.8
Graph (Binary Tree) Test9.916.015.820.012.918.0
Multithreading Test11.933.711.529.011.731.4
All Tests8.725.913.131.110.928.5

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
 DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
Basic Person Test39.14.47.51.423.32.9
Element Collection Test46.04.16.72.426.33.2
Inheritance Test7.73.43.82.05.72.7
Indexing Test0.05313.08.022.84.017.9
Multithreading Testfailed1.0failed0.67failed0.85
All Tests23.25.26.55.914.85.5

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
 DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
Basic Person Test4.016.63.87.63.912.1
Element Collection Test3.715.34.510.54.112.9
Inheritance Test4.415.74.89.84.612.7
Indexing Test5.212.14.29.94.711.0
Graph (Binary Tree) Test2.713.71.57.02.110.3
Multithreading Testfailed20.9failed4.2failed12.6
All Tests4.015.73.78.23.912.0

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
 DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
Basic Person Test3.535.11.319.62.427.4
Element Collection Test1.919.31.68.51.713.9
Inheritance Test2.436.01.314.01.925.0
Indexing Test6.642.51.919.24.330.9
Graph (Binary Tree) Test0.8112.20.9314.40.8713.3
Multithreading Testfailed54.4failed25.8failed40.1
All Tests3.033.31.416.92.225.1

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
 DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
Basic Person Test53.336.253.339.253.337.7
Element Collection Test42.633.342.634.942.634.1
Inheritance Test48.135.448.136.248.135.8
Indexing Test62.339.863.343.762.841.7
Graph (Binary Tree) Test13.641.010.228.411.934.7
Multithreading Test52.048.78.012.430.030.6
All Tests45.339.137.632.541.535.8

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
 DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
DataNucleus
Derby embedded
EclipseLink
H2 embedded
Basic Person Test11.622.36.113.38.817.8
Element Collection Test11.915.74.411.48.113.6
Inheritance Test5.623.55.514.95.519.2
Indexing Test5.725.56.621.56.223.5
Graph (Binary Tree) Test3.714.94.914.04.314.5
Multithreading Test10.328.17.414.28.821.1
All Tests8.021.95.714.96.918.4

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