Compare with

Comparison of DataNucleus with Derby embedded 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
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
Basic Person Test4.63.82.83.13.73.4
Element Collection Test2.42.21.61.52.01.8
Inheritance Test4.63.92.72.93.73.4
Indexing Test7.65.24.84.36.24.7
Graph (Binary Tree) Test1.61.91.41.71.51.8
Multithreading Test8.66.13.33.95.95.0
All Tests4.93.82.82.93.83.4

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
Basic Person Test6.86.414.911.310.98.8
Element Collection Test5.41.87.62.46.52.1
Inheritance Test8.83.714.812.911.88.3
Indexing Test9.23.614.112.811.68.2
Graph (Binary Tree) Test9.90.6115.80.7312.90.67
Multithreading Test11.98.511.519.811.714.1
All Tests8.74.113.110.010.97.0

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

A huge performance gap has been detected 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 Derby embedded database (15.8) reveals that in that case, DataNucleus with Derby embedded is 21.6 times faster than EclipseLink with Derby server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
Basic Person Test39.145.87.55.323.325.6
Element Collection Test46.035.26.70.9926.318.1
Inheritance Test7.723.13.85.95.714.5
Indexing Test0.0532.58.012.24.07.4
Multithreading Testfailed34.3failed7.7failed21.0
All Tests23.228.26.56.414.817.3

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

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

A huge performance gap has been detected 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 Derby database server (2.5) reveals that in that case, EclipseLink with Derby server is 47.2 times faster than DataNucleus with Derby embedded.

On the other hand, EclipseLink with Derby server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (0.99) to the normalized speed of DataNucleus with Derby embedded database (6.7) reveals that in that case, EclipseLink with Derby server is 6.8 times slower than DataNucleus with Derby embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
Basic Person Test4.03.93.84.43.94.1
Element Collection Test3.71.74.51.64.11.6
Inheritance Test4.44.64.86.14.65.3
Indexing Test5.24.54.27.64.76.1
Graph (Binary Tree) Test2.70.701.50.422.10.56
Multithreading Testfailed7.3failed4.8failed6.0
All Tests4.03.83.74.23.94.0

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

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

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 Derby embedded database (2.7) reveals that in that case, EclipseLink with Derby server is 3.9 times slower 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
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
Basic Person Test3.52.81.33.92.43.3
Element Collection Test1.91.21.60.551.70.87
Inheritance Test2.43.31.33.71.93.5
Indexing Test6.64.91.93.54.34.2
Graph (Binary Tree) Test0.810.510.930.500.870.51
Multithreading Testfailed4.8failed5.7failed5.3
All Tests3.02.91.43.02.23.0

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

The results above show that in general EclipseLink with Derby server is more efficient than DataNucleus with Derby embedded 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 Derby embedded database (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 Derby embedded.

On the other hand, EclipseLink with Derby server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with Derby database server (0.55) to the normalized speed of DataNucleus with Derby embedded database (1.6) reveals that in that case, EclipseLink with Derby server is 2.9 times slower than DataNucleus with Derby embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
DataNucleus
Derby embedded
EclipseLink
Derby server
Basic Person Test11.612.56.15.68.89.1
Element Collection Test11.98.44.41.48.14.9
Inheritance Test5.67.75.56.35.57.0
Indexing Test5.74.16.68.16.26.1
Graph (Binary Tree) Test3.70.934.90.834.30.88
Multithreading Test10.312.27.48.48.810.3
All Tests8.07.95.75.26.96.6

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

A large performance gap has been detected 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 Derby embedded database (4.9) reveals that in that case, DataNucleus with Derby embedded is 5.9 times faster than EclipseLink with Derby server.

Other Head to Head DBMS/JPA Comparisons