Compare with

Comparison of DataNucleus with Derby server vs EclipseLink with H2 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 server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
Basic Person Test2.85.62.32.52.64.0
Element Collection Test0.714.20.351.50.532.8
Inheritance Test2.76.62.02.12.34.4
Indexing Test4.59.74.04.14.36.9
Graph (Binary Tree) Test0.624.70.533.50.574.1
Multithreading Test4.910.23.44.04.17.1
All Tests2.76.82.12.92.44.9

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
Basic Person Test0.565.56.38.23.46.8
Element Collection Test0.363.20.934.20.643.7
Inheritance Test0.454.76.810.13.67.4
Indexing Test0.504.47.19.43.86.9
Graph (Binary Tree) Test0.221.16.61.93.41.5
Multithreading Test1.212.210.015.95.614.0
All Tests0.555.26.38.33.46.7

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

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.45) to the normalized speed of EclipseLink with H2 database server (4.7) reveals that in that case, EclipseLink with H2 server is 10.4 times faster than DataNucleus with Derby server.

On the other hand, EclipseLink with H2 server is slower, for instance, when using graphs of objects with large retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (1.9) to the normalized speed of DataNucleus with Derby database server (6.6) reveals that in that case, EclipseLink with H2 server is 3.5 times slower than DataNucleus with Derby server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
Basic Person Test37.73.83.61.120.72.5
Element Collection Test25.94.11.41.113.62.6
Inheritance Test6.53.21.81.34.22.3
Indexing Test0.0303.04.98.02.55.5
Multithreading Testfailed1.1failed1.0failed1.1
All Tests17.53.02.92.510.22.8

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

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

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

On the other hand, DataNucleus with Derby server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.030) to the normalized speed of EclipseLink with H2 database server (3.0) reveals that in that case, DataNucleus with Derby server is 100 times slower than EclipseLink with H2 server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
Basic Person Test1.14.50.852.20.993.4
Element Collection Test0.813.80.622.40.713.1
Inheritance Test1.24.41.33.01.23.7
Indexing Test1.24.21.53.11.33.7
Graph (Binary Tree) Test0.291.40.410.790.351.1
Multithreading Testfailed7.8failed2.5failed5.1
All Tests0.934.30.922.30.923.3

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

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
Basic Person Test1.36.41.33.11.34.8
Element Collection Test0.613.00.331.30.472.2
Inheritance Test1.05.61.32.81.24.2
Indexing Test2.310.31.93.82.17.0
Graph (Binary Tree) Test0.261.50.461.30.361.4
Multithreading Testfailed7.0failed4.9failed6.0
All Tests1.15.61.12.91.14.3

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

The results above show that in general EclipseLink with H2 server is much more efficient than DataNucleus with Derby server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby database server (1.1) to the normalized speed of EclipseLink with H2 database server (4.3) reveals that in these tests, EclipseLink with H2 server is 3.9 times faster than DataNucleus with Derby server.

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
DataNucleus
Derby server
EclipseLink
H2 server
Basic Person Test8.75.22.93.45.84.3
Element Collection Test5.73.60.722.13.22.9
Inheritance Test2.44.92.63.92.54.4
Indexing Test1.76.33.95.72.86.0
Graph (Binary Tree) Test0.352.12.01.91.22.0
Multithreading Test3.07.76.75.74.96.7
All Tests3.85.12.83.83.34.5

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

A large performance gap has been detected when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.35) to the normalized speed of EclipseLink with H2 database server (2.1) reveals that in that case, EclipseLink with H2 server is 6.0 times faster than DataNucleus with Derby server.

Other Head to Head DBMS/JPA Comparisons