Compare with

Comparison of EclipseLink with H2 server vs DataNucleus with PostgreSQL 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
 EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
Basic Person Test5.64.12.52.64.03.3
Element Collection Test4.20.911.50.382.80.64
Inheritance Test6.63.82.12.44.43.1
Indexing Test9.76.04.16.46.96.2
Graph (Binary Tree) Test4.70.913.50.774.10.84
Multithreading Test10.218.04.08.37.113.1
All Tests6.85.62.93.54.94.5

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

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

On the other hand, EclipseLink with H2 server is slower, for instance, when using multithreading with large transaction size. Comparing the normalized speed of EclipseLink with H2 database server (4.0) to the normalized speed of DataNucleus with PostgreSQL database server (8.3) reveals that in that case, EclipseLink with H2 server is 2.1 times slower than DataNucleus with PostgreSQL server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
Basic Person Test5.51.78.27.66.84.6
Element Collection Test3.20.734.20.633.70.68
Inheritance Test4.71.510.19.37.45.4
Indexing Test4.41.59.49.26.95.3
Graph (Binary Tree) Test1.12.61.912.31.57.4
Multithreading Test12.23.415.910.814.07.1
All Tests5.21.98.38.36.75.1

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

A large performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.63) to the normalized speed of EclipseLink with H2 database server (4.2) reveals that in that case, EclipseLink with H2 server is 6.7 times faster than DataNucleus with PostgreSQL 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 PostgreSQL database server (12.3) reveals that in that case, EclipseLink with H2 server is 6.5 times slower than DataNucleus with PostgreSQL server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
Basic Person Test3.849.11.14.72.526.9
Element Collection Test4.139.11.10.482.619.8
Inheritance Test3.255.91.36.62.331.2
Indexing Test3.00.0488.06.45.53.2
Multithreading Test1.1failed1.0failed1.1failed
All Tests3.036.02.54.52.820.3

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

The results above show that in general DataNucleus with PostgreSQL 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 PostgreSQL database server (20.3) reveals that in these tests, DataNucleus with PostgreSQL server is 7.3 times faster than EclipseLink with H2 server.

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

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.048) to the normalized speed of EclipseLink with H2 database server (3.0) reveals that in that case, DataNucleus with PostgreSQL server is 62.5 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
 EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
Basic Person Test4.52.12.20.843.41.5
Element Collection Test3.81.42.40.643.11.0
Inheritance Test4.42.13.01.23.71.7
Indexing Test4.22.23.11.53.71.8
Graph (Binary Tree) Test1.40.650.790.201.10.42
Multithreading Test7.80.462.5failed5.10.46
All Tests4.31.52.30.873.31.2

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

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

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.46) to the normalized speed of EclipseLink with H2 database server (7.8) reveals that in that case, EclipseLink with H2 server is 17.0 times faster than DataNucleus with PostgreSQL server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
Basic Person Test6.43.03.11.34.82.2
Element Collection Test3.01.01.30.392.20.69
Inheritance Test5.62.82.81.34.22.1
Indexing Test10.35.43.81.97.03.7
Graph (Binary Tree) Test1.50.381.30.371.40.37
Multithreading Test7.013.84.9failed6.013.8
All Tests5.64.42.91.14.32.9

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

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
EclipseLink
H2 server
DataNucleus
PostgreSQL server
Basic Person Test5.212.03.43.44.37.7
Element Collection Test3.68.62.10.502.94.6
Inheritance Test4.913.23.94.24.48.7
Indexing Test6.33.05.75.16.04.0
Graph (Binary Tree) Test2.11.11.93.42.02.3
Multithreading Test7.78.95.79.56.79.1
All Tests5.18.03.83.84.56.0

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

A large performance gap has been detected when using class inheritance in the object model with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (4.9) to the normalized speed of DataNucleus with PostgreSQL database server (13.2) reveals that in that case, DataNucleus with PostgreSQL server is 2.7 times faster than EclipseLink with H2 server.

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.50) to the normalized speed of EclipseLink with H2 database server (2.1) reveals that in that case, DataNucleus with PostgreSQL server is 4.2 times slower than EclipseLink with H2 server.

Other Head to Head DBMS/JPA Comparisons