Compare with

Comparison of DataNucleus with DB4O embedded vs EclipseLink with Derby 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
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
Basic Person Test0.0593.81.33.10.693.4
Element Collection Test0.0452.21.01.50.521.8
Inheritance Test0.0513.90.852.90.453.4
Indexing Test0.0805.22.34.31.24.7
Graph (Binary Tree) Testfailed1.9failed1.7failed1.8
Multithreading Testfailed6.1failed3.9failed5.0
All Tests0.0593.81.42.90.713.4

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

The results above show that in general EclipseLink with Derby 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 Derby database server (3.4) reveals that in these tests, EclipseLink with Derby server is 4.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 transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.051) to the normalized speed of EclipseLink with Derby database server (3.9) reveals that in that case, EclipseLink with Derby server is 76.5 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
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
Basic Person Test0.00476.41.811.30.908.8
Element Collection Test0.00381.81.52.40.772.1
Inheritance Test0.00353.72.212.91.18.3
Indexing Test0.00433.61.812.80.898.2
Graph (Binary Tree) Testfailed0.61failed0.73failed0.67
Multithreading Testfailed8.5failed19.8failed14.1
All Tests0.00414.11.810.00.917.0

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

The results above show that in general EclipseLink with Derby 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 Derby database server (7.0) reveals that in these tests, EclipseLink with Derby server is 7.7 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using simple basic entities with small retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0047) to the normalized speed of EclipseLink with Derby database server (6.4) reveals that in that case, EclipseLink with Derby server is 1,362 times faster 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
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
Basic Person Testfailed45.8failed5.3failed25.6
Element Collection Testfailed35.2failed0.99failed18.1
Inheritance Testfailed23.1failed5.9failed14.5
Indexing Testfailed2.5failed12.2failed7.4
Multithreading Testfailed34.3failed7.7failed21.0
All Testsfailed28.2failed6.4failed17.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
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
Basic Person Test0.0123.90.764.40.394.1
Element Collection Test0.0121.71.11.60.531.6
Inheritance Test0.0114.60.816.10.415.3
Indexing Test0.0114.51.37.60.646.1
Graph (Binary Tree) Testfailed0.70failed0.42failed0.56
Multithreading Testfailed7.3failed4.8failed6.0
All Tests0.0123.80.974.20.494.0

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

The results above show that in general EclipseLink with Derby 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 Derby database server (4.0) reveals that in these tests, EclipseLink with Derby server is 8.2 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.011) to the normalized speed of EclipseLink with Derby database server (4.6) reveals that in that case, EclipseLink with Derby server is 418 times faster 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
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
Basic Person Test0.0112.81.53.90.743.3
Element Collection Test0.0101.21.60.550.800.87
Inheritance Test0.00933.31.13.70.573.5
Indexing Test0.0174.92.13.51.14.2
Graph (Binary Tree) Testfailed0.51failed0.50failed0.51
Multithreading Testfailed4.8failed5.7failed5.3
All Tests0.0122.91.63.00.793.0

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

The results above show that in general EclipseLink with Derby 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 Derby database server (3.0) reveals that in these tests, EclipseLink with Derby server is 3.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 transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0093) to the normalized speed of EclipseLink with Derby database server (3.3) reveals that in that case, EclipseLink with Derby server is 355 times faster than DataNucleus with DB4O embedded.

On the other hand, EclipseLink with Derby server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with Derby database server (0.55) to the normalized speed of DataNucleus with DB4O embedded database (1.6) reveals that in that case, EclipseLink with Derby server is 2.9 times slower 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
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
DataNucleus
DB4O embedded
EclipseLink
Derby server
Basic Person Test0.02212.51.35.60.689.1
Element Collection Test0.0188.41.31.40.664.9
Inheritance Test0.0197.71.26.30.637.0
Indexing Test0.0284.11.98.10.946.1
Graph (Binary Tree) Testfailed0.93failed0.83failed0.88
Multithreading Testfailed12.2failed8.4failed10.3
All Tests0.0227.91.45.20.736.6

The results above show that in general EclipseLink with Derby 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 Derby database server (6.6) reveals that in these tests, EclipseLink with Derby server is 9.0 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using simple basic entities with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.022) to the normalized speed of EclipseLink with Derby database server (12.5) reveals that in that case, EclipseLink with Derby server is 568 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons