Compare with

Comparison of DataNucleus with MySQL 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
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
Basic Person Test2.65.61.42.52.04.0
Element Collection Test1.04.20.481.50.762.8
Inheritance Test2.56.61.32.11.94.4
Indexing Test4.09.72.54.13.36.9
Graph (Binary Tree) Test1.14.70.993.51.14.1
Multithreading Test6.210.22.54.04.47.1
All Tests2.96.81.52.92.24.9

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
Basic Person Test0.965.59.38.25.16.8
Element Collection Test0.183.20.774.20.473.7
Inheritance Test0.554.78.510.14.57.4
Indexing Test0.824.49.79.45.36.9
Graph (Binary Tree) Test2.11.13.51.92.81.5
Multithreading Test0.2712.27.815.94.014.0
All Tests0.815.26.68.33.76.7

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

A huge performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.27) to the normalized speed of EclipseLink with H2 database server (12.2) reveals that in that case, EclipseLink with H2 server is 45.2 times faster than DataNucleus with MySQL server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
Basic Person Test7.23.82.21.14.72.5
Element Collection Test5.84.10.271.13.12.6
Inheritance Test2.93.21.71.32.32.3
Indexing Test0.00843.02.58.01.25.5
Multithreading Testfailed1.1failed1.0failed1.1
All Tests4.03.01.72.52.82.8

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

The results above show that in general DataNucleus with MySQL server is equivalent to EclipseLink with H2 server in executing the tested JPA queries.

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

On the other hand, DataNucleus with MySQL server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.0084) to the normalized speed of EclipseLink with H2 database server (3.0) reveals that in that case, DataNucleus with MySQL server is 357 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
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
Basic Person Test0.614.51.12.20.883.4
Element Collection Test0.313.80.442.40.383.1
Inheritance Test0.514.41.83.01.13.7
Indexing Test0.684.22.23.11.53.7
Graph (Binary Tree) Test0.911.40.470.790.691.1
Multithreading Test0.647.8failed2.50.645.1
All Tests0.614.31.22.30.883.3

DataNucleus with MySQL server has failed in 1 tests (see exceptions).

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (0.31) to the normalized speed of EclipseLink with H2 database server (3.8) reveals that in that case, EclipseLink with H2 server is 12.3 times faster than DataNucleus with MySQL server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
Basic Person Test0.706.41.33.11.04.8
Element Collection Test0.173.00.401.30.292.2
Inheritance Test0.415.61.32.80.874.2
Indexing Test1.710.31.93.81.87.0
Graph (Binary Tree) Test0.491.50.461.30.471.4
Multithreading Testfailed7.0failed4.9failed6.0
All Tests0.695.61.12.90.894.3

DataNucleus with MySQL 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 MySQL server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with MySQL database server (0.89) to the normalized speed of EclipseLink with H2 database server (4.3) reveals that in these tests, EclipseLink with H2 server is 4.8 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (0.17) to the normalized speed of EclipseLink with H2 database server (3.0) reveals that in that case, EclipseLink with H2 server is 17.6 times faster than DataNucleus with MySQL server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
DataNucleus
MySQL server
EclipseLink
H2 server
Basic Person Test2.45.23.13.42.74.3
Element Collection Test1.53.60.472.10.992.9
Inheritance Test1.44.92.93.92.14.4
Indexing Test1.46.33.85.72.66.0
Graph (Binary Tree) Test1.22.11.41.91.32.0
Multithreading Test2.47.75.15.73.56.7
All Tests1.75.12.63.82.14.5

The results above show that in general EclipseLink with H2 server is more efficient than DataNucleus with MySQL server in performing JPA database operations. Comparing the normalized speed of DataNucleus with MySQL database server (2.1) to the normalized speed of EclipseLink with H2 database server (4.5) reveals that in these tests, EclipseLink with H2 server is 2.1 times faster than DataNucleus with MySQL server.

A large performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (1.4) to the normalized speed of EclipseLink with H2 database server (6.3) reveals that in that case, EclipseLink with H2 server is 4.5 times faster than DataNucleus with MySQL server.

Other Head to Head DBMS/JPA Comparisons