Compare with

Comparison of DataNucleus with HSQLDB embedded vs EclipseLink 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
 DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
Basic Person Test14.25.54.83.79.54.6
Element Collection Test6.63.02.11.74.32.4
Inheritance Test13.65.34.63.59.14.4
Indexing Test24.66.911.14.617.85.8
Graph (Binary Tree) Test6.82.04.51.95.71.9
Multithreading Test38.59.38.54.123.56.7
All Tests17.45.35.93.211.74.3

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

A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (9.3) to the normalized speed of DataNucleus with HSQLDB embedded database (38.5) reveals that in that case, DataNucleus with HSQLDB embedded is 4.1 times faster than EclipseLink with Derby embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
Basic Person Test6.616.410.258.78.437.5
Element Collection Test3.67.58.113.35.810.4
Inheritance Test5.717.18.858.97.238.0
Indexing Test5.114.29.567.47.340.8
Graph (Binary Tree) Test7.22.89.35.78.34.2
Multithreading Test8.128.09.548.78.838.4
All Tests6.014.39.242.17.628.2

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

A large performance gap has been detected when using database indexes with large retrieval size. Comparing the normalized speed of DataNucleus with HSQLDB embedded database (9.5) to the normalized speed of EclipseLink with Derby embedded database (67.4) reveals that in that case, EclipseLink with Derby embedded is 7.1 times faster than DataNucleus with HSQLDB embedded.

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using graphs of objects with small retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (2.8) to the normalized speed of DataNucleus with HSQLDB embedded database (7.2) reveals that in that case, EclipseLink with Derby embedded is 2.6 times slower than DataNucleus with HSQLDB embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
Basic Person Test1.453.40.4813.80.9533.6
Element Collection Test1.337.90.674.41.021.2
Inheritance Test1.637.40.6115.01.126.2
Indexing Test0.00167.60.6349.30.3228.4
Multithreading Test0.4041.2failed6.10.4023.6
All Tests0.9635.50.6017.70.8026.6

DataNucleus with HSQLDB embedded has failed in 1 tests (see exceptions).

The results above show that in general EclipseLink with Derby embedded is much more efficient than DataNucleus with HSQLDB embedded in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with HSQLDB embedded database (0.80) to the normalized speed of EclipseLink with Derby embedded database (26.6) reveals that in these tests, EclipseLink with Derby embedded is 33.2 times faster than DataNucleus with HSQLDB embedded.

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with HSQLDB embedded database (0.0016) to the normalized speed of EclipseLink with Derby embedded database (7.6) reveals that in that case, EclipseLink with Derby embedded is 4,750 times faster than DataNucleus with HSQLDB embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
Basic Person Test11.56.42.76.77.16.5
Element Collection Test6.95.42.76.24.85.8
Inheritance Test10.36.53.69.26.97.8
Indexing Test11.47.34.411.17.99.2
Graph (Binary Tree) Test3.52.81.51.72.52.2
Multithreading Testfailed21.3failed5.0failed13.1
All Tests8.78.33.06.65.87.5

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

The results above show that in general EclipseLink with Derby embedded is slightly more efficient than DataNucleus with HSQLDB embedded in updating JPA entity objects in 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 HSQLDB embedded database (3.6) to the normalized speed of EclipseLink with Derby embedded database (9.2) reveals that in that case, EclipseLink with Derby embedded is 2.6 times faster than DataNucleus with HSQLDB embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
Basic Person Test4.24.61.34.72.84.6
Element Collection Test4.92.51.61.43.21.9
Inheritance Test4.03.91.34.52.74.2
Indexing Test7.56.21.93.84.75.0
Graph (Binary Tree) Test2.91.12.01.02.51.1
Multithreading Test40.16.213.75.826.96.0
All Tests10.64.13.73.57.13.8

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

A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (6.2) to the normalized speed of DataNucleus with HSQLDB embedded database (40.1) reveals that in that case, DataNucleus with HSQLDB embedded is 6.5 times faster than EclipseLink with Derby embedded.

On the other hand, DataNucleus with HSQLDB embedded is slower, for instance, when using simple basic entities with large transaction size. Comparing the normalized speed of DataNucleus with HSQLDB embedded database (1.3) to the normalized speed of EclipseLink with Derby embedded database (4.7) reveals that in that case, DataNucleus with HSQLDB embedded is 3.6 times slower than EclipseLink with Derby embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
Basic Person Test41.451.141.451.041.451.1
Element Collection Test23.438.523.439.423.438.9
Inheritance Test41.448.041.447.941.448.0
Indexing Test48.451.649.252.348.852.0
Graph (Binary Tree) Test12.513.49.411.710.912.6
Multithreading Test51.952.610.38.431.130.5
All Tests36.542.529.235.132.938.8

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
DataNucleus
HSQLDB embedded
EclipseLink
Derby embedded
Basic Person Test7.617.33.917.55.717.4
Element Collection Test4.711.33.05.43.88.3
Inheritance Test7.114.03.818.25.416.1
Indexing Test9.78.45.527.27.617.8
Graph (Binary Tree) Test5.12.24.32.64.72.4
Multithreading Test21.821.210.613.917.017.6
All Tests9.012.74.814.57.013.6

The results above show that in general EclipseLink with Derby embedded is more efficient than DataNucleus with HSQLDB embedded in performing JPA database operations.

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

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (2.2) to the normalized speed of DataNucleus with HSQLDB embedded database (5.1) reveals that in that case, EclipseLink with Derby embedded is 2.3 times slower than DataNucleus with HSQLDB embedded.

Other Head to Head DBMS/JPA Comparisons