Compare with

Comparison of DataNucleus with H2 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
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
Basic Person Test19.23.88.03.113.63.4
Element Collection Test6.62.22.81.54.71.8
Inheritance Test15.63.94.42.910.03.4
Indexing Test24.45.211.84.318.14.7
Graph (Binary Tree) Test9.21.96.21.77.71.8
Multithreading Test34.96.17.13.921.05.0
All Tests18.33.86.72.912.53.4

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
Basic Person Test13.26.413.511.313.38.8
Element Collection Test6.41.88.92.47.72.1
Inheritance Test12.23.712.712.912.48.3
Indexing Test8.13.616.512.812.38.2
Graph (Binary Tree) Test10.60.6120.90.7315.80.67
Multithreading Test13.38.59.919.811.614.1
All Tests10.64.113.710.012.27.0

The results above show that in general DataNucleus with H2 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 H2 embedded database (20.9) reveals that in that case, DataNucleus with H2 embedded is 28.6 times faster than EclipseLink with Derby server.

On the other hand, DataNucleus with H2 embedded is slower, for instance, when using multithreading with large retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (9.9) to the normalized speed of EclipseLink with Derby database server (19.8) reveals that in that case, DataNucleus with H2 embedded is 2.0 times slower than EclipseLink with Derby server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
Basic Person Test4.745.81.45.33.125.6
Element Collection Test5.035.22.40.993.718.1
Inheritance Test3.823.11.65.92.714.5
Indexing Test0.00412.51.812.20.917.4
Multithreading Test1.234.30.797.71.021.0
All Tests3.028.21.66.42.317.3

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

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (0.0041) to the normalized speed of EclipseLink with Derby database server (2.5) reveals that in that case, EclipseLink with Derby server is 610 times faster than DataNucleus with H2 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 H2 embedded database (2.4) reveals that in that case, EclipseLink with Derby server is 2.4 times slower than DataNucleus with H2 embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
Basic Person Test10.03.93.94.46.94.1
Element Collection Test7.61.73.91.65.81.6
Inheritance Test9.44.64.46.16.95.3
Indexing Test10.64.55.97.68.26.1
Graph (Binary Tree) Test5.90.703.70.424.80.56
Multithreading Testfailed7.3failed4.8failed6.0
All Tests8.73.84.44.26.54.0

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

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
Basic Person Test4.22.81.33.92.83.3
Element Collection Test4.91.21.60.553.20.87
Inheritance Test4.03.31.33.72.73.5
Indexing Test7.54.91.93.54.74.2
Graph (Binary Tree) Test5.60.514.10.504.80.51
Multithreading Testfailed4.8failed5.7failed5.3
All Tests5.22.92.03.03.63.0

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

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

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
DataNucleus
H2 embedded
EclipseLink
Derby server
Basic Person Test10.312.55.65.67.99.1
Element Collection Test6.18.43.91.45.04.9
Inheritance Test9.07.74.96.36.97.0
Indexing Test10.14.17.68.18.96.1
Graph (Binary Tree) Test7.80.938.70.838.30.88
Multithreading Test16.512.25.98.411.210.3
All Tests9.67.96.05.27.86.6

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

A huge 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 H2 embedded database (8.7) reveals that in that case, DataNucleus with H2 embedded is 10.5 times faster than EclipseLink with Derby server.

Other Head to Head DBMS/JPA Comparisons