Compare with

Comparison of DataNucleus with DB4O embedded 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
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
Basic Person Test0.0597.31.34.20.695.8
Element Collection Test0.0453.11.01.90.522.5
Inheritance Test0.0516.90.855.00.455.9
Indexing Test0.08010.02.36.81.28.4
Graph (Binary Tree) Testfailed3.5failed3.3failed3.4
Multithreading Testfailed31.8failed14.5failed23.1
All Tests0.05910.41.46.00.718.2

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with DB4O embedded in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.71) to the normalized speed of EclipseLink with PostgreSQL database server (8.2) reveals that in these tests, EclipseLink with PostgreSQL server is 11.5 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.051) to the normalized speed of EclipseLink with PostgreSQL database server (6.9) reveals that in that case, EclipseLink with PostgreSQL server is 135 times faster than DataNucleus with DB4O embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
Basic Person Test0.00476.81.817.20.9012.0
Element Collection Test0.00380.0261.50.0200.770.023
Inheritance Test0.00356.02.219.71.112.9
Indexing Test0.00435.61.819.50.8912.6
Graph (Binary Tree) Testfailed0.47failed0.61failed0.54
Multithreading Testfailed13.5failed27.8failed20.6
All Tests0.00415.41.814.10.919.8

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

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 DB4O embedded database (0.0035) to the normalized speed of EclipseLink with PostgreSQL database server (6.0) reveals that in that case, EclipseLink with PostgreSQL server is 1,714 times faster than DataNucleus with DB4O embedded.

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 DB4O embedded database (1.5) reveals that in that case, EclipseLink with PostgreSQL server is 75.0 times slower than DataNucleus with DB4O embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
Basic Person Testfailed55.5failed7.8failed31.6
Element Collection Testfailed15.4failed0.028failed7.7
Inheritance Testfailed54.9failed11.5failed33.2
Indexing Testfailed0.077failed10.0failed5.1
Multithreading Testfailed55.3failed12.0failed33.7
All Testsfailed36.2failed8.3failed22.3

DataNucleus with DB4O embedded has failed in 10 tests (see exceptions).

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
Basic Person Test0.0126.20.764.10.395.1
Element Collection Test0.0120.0801.10.0280.530.054
Inheritance Test0.0116.40.816.10.416.2
Indexing Test0.0116.51.37.00.646.8
Graph (Binary Tree) Testfailed0.90failed0.50failed0.70
Multithreading Testfailed36.0failed9.1failed22.5
All Tests0.0129.30.974.50.496.9

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with DB4O embedded in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.49) to the normalized speed of EclipseLink with PostgreSQL database server (6.9) reveals that in these tests, EclipseLink with PostgreSQL server is 14.1 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.011) to the normalized speed of EclipseLink with PostgreSQL database server (6.5) reveals that in that case, EclipseLink with PostgreSQL server is 591 times faster than DataNucleus with DB4O embedded.

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 DB4O embedded database (1.1) reveals that in that case, EclipseLink with PostgreSQL server is 39.3 times slower than DataNucleus with DB4O embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
Basic Person Test0.0115.71.55.70.745.7
Element Collection Test0.0100.0251.6stopped0.800.012
Inheritance Test0.00935.51.15.40.575.4
Indexing Test0.01710.42.110.01.110.2
Graph (Binary Tree) Testfailed0.016failed0.013failed0.015
Multithreading Testfailed26.3failed16.8failed21.6
All Tests0.0128.01.66.30.797.2

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.017) to the normalized speed of EclipseLink with PostgreSQL database server (10.4) reveals that in that case, EclipseLink with PostgreSQL server is 612 times faster than DataNucleus with DB4O embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
DataNucleus
DB4O embedded
EclipseLink
PostgreSQL server
Basic Person Test0.02216.31.37.80.6812.1
Element Collection Test0.0183.71.30.400.662.1
Inheritance Test0.01915.91.29.50.6312.7
Indexing Test0.0286.51.910.70.948.6
Graph (Binary Tree) Testfailed1.2failed1.1failed1.2
Multithreading Testfailed32.6failed16.0failed24.3
All Tests0.02213.11.47.80.7310.5

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.019) to the normalized speed of EclipseLink with PostgreSQL database server (15.9) reveals that in that case, EclipseLink with PostgreSQL server is 837 times faster than DataNucleus with DB4O embedded.

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

Other Head to Head DBMS/JPA Comparisons