Compare with

Comparison of DataNucleus with PostgreSQL server vs EclipseLink 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
 DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
Basic Person Test4.17.32.64.23.35.8
Element Collection Test0.913.10.381.90.642.5
Inheritance Test3.86.92.45.03.15.9
Indexing Test6.010.06.46.86.28.4
Graph (Binary Tree) Test0.913.50.773.30.843.4
Multithreading Test18.031.88.314.513.123.1
All Tests5.610.43.56.04.58.2

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

A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.38) to the normalized speed of EclipseLink with PostgreSQL database server (1.9) reveals that in that case, EclipseLink with PostgreSQL server is 5.0 times faster than DataNucleus with PostgreSQL server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
Basic Person Test1.76.87.617.24.612.0
Element Collection Test0.730.0260.630.0200.680.023
Inheritance Test1.56.09.319.75.412.9
Indexing Test1.55.69.219.55.312.6
Graph (Binary Tree) Test2.60.4712.30.617.40.54
Multithreading Test3.413.510.827.87.120.6
All Tests1.95.48.314.15.19.8

The results above show that in general EclipseLink with PostgreSQL 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 simple basic entities with small retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (1.7) to the normalized speed of EclipseLink with PostgreSQL database server (6.8) reveals that in that case, EclipseLink with PostgreSQL server is 4.0 times faster than DataNucleus with PostgreSQL server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.020) to the normalized speed of DataNucleus with PostgreSQL database server (0.63) reveals that in that case, EclipseLink with PostgreSQL server is 31.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
 DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
Basic Person Test49.155.54.77.826.931.6
Element Collection Test39.115.40.480.02819.87.7
Inheritance Test55.954.96.611.531.233.2
Indexing Test0.0480.0776.410.03.25.1
Multithreading Testfailed55.3failed12.0failed33.7
All Tests36.036.24.58.320.322.3

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

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
Basic Person Test2.16.20.844.11.55.1
Element Collection Test1.40.0800.640.0281.00.054
Inheritance Test2.16.41.26.11.76.2
Indexing Test2.26.51.57.01.86.8
Graph (Binary Tree) Test0.650.900.200.500.420.70
Multithreading Test0.4636.0failed9.10.4622.5
All Tests1.59.30.874.51.26.9

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

The results above show that in general EclipseLink with PostgreSQL server is much 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 PostgreSQL database server (6.9) reveals that in these tests, EclipseLink with PostgreSQL server is 5.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 PostgreSQL database server (36.0) reveals that in that case, EclipseLink with PostgreSQL server is 78.3 times faster than DataNucleus with PostgreSQL server.

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
Basic Person Test3.05.71.35.72.25.7
Element Collection Test1.00.0250.39stopped0.690.012
Inheritance Test2.85.51.35.42.15.4
Indexing Test5.410.41.910.03.710.2
Graph (Binary Tree) Test0.380.0160.370.0130.370.015
Multithreading Test13.826.3failed16.813.821.6
All Tests4.48.01.16.32.97.2

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

The results above show that in general EclipseLink with PostgreSQL server is more efficient than DataNucleus with PostgreSQL server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with PostgreSQL database server (2.9) to the normalized speed of EclipseLink with PostgreSQL database server (7.2) reveals that in these tests, EclipseLink with PostgreSQL server is 2.5 times faster than DataNucleus with PostgreSQL server.

A large performance gap has been detected when using database indexes with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (1.9) to the normalized speed of EclipseLink with PostgreSQL database server (10.0) reveals that in that case, EclipseLink with PostgreSQL server is 5.3 times faster than DataNucleus with PostgreSQL server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.025) to the normalized speed of DataNucleus with PostgreSQL database server (1.0) reveals that in that case, EclipseLink with PostgreSQL server is 40.0 times slower than DataNucleus with PostgreSQL server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
DataNucleus
PostgreSQL server
EclipseLink
PostgreSQL server
Basic Person Test12.016.33.47.87.712.1
Element Collection Test8.63.70.500.404.62.1
Inheritance Test13.215.94.29.58.712.7
Indexing Test3.06.55.110.74.08.6
Graph (Binary Tree) Test1.11.23.41.12.31.2
Multithreading Test8.932.69.516.09.124.3
All Tests8.013.13.87.86.010.5

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

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (8.9) to the normalized speed of EclipseLink with PostgreSQL database server (32.6) reveals that in that case, EclipseLink with PostgreSQL server is 3.7 times faster than DataNucleus with PostgreSQL server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using graphs of objects with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (1.1) to the normalized speed of DataNucleus with PostgreSQL database server (3.4) reveals that in that case, EclipseLink with PostgreSQL server is 3.1 times slower than DataNucleus with PostgreSQL server.

Other Head to Head DBMS/JPA Comparisons