Compare with

Comparison of DataNucleus with PostgreSQL server vs EclipseLink with Derby embedded

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
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
Basic Person Test4.15.52.63.73.34.6
Element Collection Test0.913.00.381.70.642.4
Inheritance Test3.85.32.43.53.14.4
Indexing Test6.06.96.44.66.25.8
Graph (Binary Tree) Test0.912.00.771.90.841.9
Multithreading Test18.09.38.34.113.16.7
All Tests5.65.33.53.24.54.3

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

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

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, 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 Derby embedded database (1.7) reveals that in that case, DataNucleus with PostgreSQL server is 4.5 times slower than EclipseLink with Derby embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
Basic Person Test1.716.47.658.74.637.5
Element Collection Test0.737.50.6313.30.6810.4
Inheritance Test1.517.19.358.95.438.0
Indexing Test1.514.29.267.45.340.8
Graph (Binary Tree) Test2.62.812.35.77.44.2
Multithreading Test3.428.010.848.77.138.4
All Tests1.914.38.342.15.128.2

The results above show that in general EclipseLink with Derby embedded is much more efficient than DataNucleus with PostgreSQL server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with PostgreSQL database server (5.1) to the normalized speed of EclipseLink with Derby embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 5.5 times faster than DataNucleus with PostgreSQL server.

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

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using graphs of objects with large retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (5.7) to the normalized speed of DataNucleus with PostgreSQL database server (12.3) reveals that in that case, EclipseLink with Derby embedded is 2.2 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
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
Basic Person Test49.153.44.713.826.933.6
Element Collection Test39.137.90.484.419.821.2
Inheritance Test55.937.46.615.031.226.2
Indexing Test0.0487.66.449.33.228.4
Multithreading Testfailed41.2failed6.1failed23.6
All Tests36.035.54.517.720.326.6

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

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

A huge performance gap has been detected 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 Derby embedded database (7.6) reveals that in that case, EclipseLink with Derby embedded is 158 times faster 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
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
Basic Person Test2.16.40.846.71.56.5
Element Collection Test1.45.40.646.21.05.8
Inheritance Test2.16.51.29.21.77.8
Indexing Test2.27.31.511.11.89.2
Graph (Binary Tree) Test0.652.80.201.70.422.2
Multithreading Test0.4621.3failed5.00.4613.1
All Tests1.58.30.876.61.27.5

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

The results above show that in general EclipseLink with Derby embedded 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 Derby embedded database (7.5) reveals that in these tests, EclipseLink with Derby embedded is 6.2 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 Derby embedded database (21.3) reveals that in that case, EclipseLink with Derby embedded is 46.3 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
 DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
Basic Person Test3.04.61.34.72.24.6
Element Collection Test1.02.50.391.40.691.9
Inheritance Test2.83.91.34.52.14.2
Indexing Test5.46.21.93.83.75.0
Graph (Binary Tree) Test0.381.10.371.00.371.1
Multithreading Test13.86.2failed5.813.86.0
All Tests4.44.11.13.52.93.8

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

The results above show that in general EclipseLink with Derby embedded 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 simple basic entities with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (1.3) to the normalized speed of EclipseLink with Derby embedded database (4.7) reveals that in that case, EclipseLink with Derby embedded is 3.6 times faster than DataNucleus with PostgreSQL server.

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (6.2) to the normalized speed of DataNucleus with PostgreSQL database server (13.8) reveals that in that case, EclipseLink with Derby embedded is 2.2 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
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
DataNucleus
PostgreSQL server
EclipseLink
Derby embedded
Basic Person Test12.017.33.417.57.717.4
Element Collection Test8.611.30.505.44.68.3
Inheritance Test13.214.04.218.28.716.1
Indexing Test3.08.45.127.24.017.8
Graph (Binary Tree) Test1.12.23.42.62.32.4
Multithreading Test8.921.29.513.99.117.6
All Tests8.012.73.814.56.013.6

The results above show that in general EclipseLink with Derby embedded is more efficient than DataNucleus with PostgreSQL server in performing JPA database operations. Comparing the normalized speed of DataNucleus with PostgreSQL database server (6.0) to the normalized speed of EclipseLink with Derby embedded database (13.6) reveals that in these tests, EclipseLink with Derby embedded is 2.3 times faster than DataNucleus with PostgreSQL server.

A huge performance gap has been detected 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 Derby embedded database (5.4) reveals that in that case, EclipseLink with Derby embedded is 10.8 times faster than DataNucleus with PostgreSQL server.

Other Head to Head DBMS/JPA Comparisons