Compare with

Comparison of DataNucleus with DB4O embedded 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
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
Basic Person Test0.0595.51.33.70.694.6
Element Collection Test0.0453.01.01.70.522.4
Inheritance Test0.0515.30.853.50.454.4
Indexing Test0.0806.92.34.61.25.8
Graph (Binary Tree) Testfailed2.0failed1.9failed1.9
Multithreading Testfailed9.3failed4.1failed6.7
All Tests0.0595.31.43.20.714.3

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (4.3) reveals that in these tests, EclipseLink with Derby embedded is 6.1 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 embedded database (5.3) reveals that in that case, EclipseLink with Derby embedded is 104 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 embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
Basic Person Test0.004716.41.858.70.9037.5
Element Collection Test0.00387.51.513.30.7710.4
Inheritance Test0.003517.12.258.91.138.0
Indexing Test0.004314.21.867.40.8940.8
Graph (Binary Tree) Testfailed2.8failed5.7failed4.2
Multithreading Testfailed28.0failed48.7failed38.4
All Tests0.004114.31.842.10.9128.2

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 31.0 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 Derby embedded database (17.1) reveals that in that case, EclipseLink with Derby embedded is 4,886 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 embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
Basic Person Testfailed53.4failed13.8failed33.6
Element Collection Testfailed37.9failed4.4failed21.2
Inheritance Testfailed37.4failed15.0failed26.2
Indexing Testfailed7.6failed49.3failed28.4
Multithreading Testfailed41.2failed6.1failed23.6
All Testsfailed35.5failed17.7failed26.6

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 embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
Basic Person Test0.0126.40.766.70.396.5
Element Collection Test0.0125.41.16.20.535.8
Inheritance Test0.0116.50.819.20.417.8
Indexing Test0.0117.31.311.10.649.2
Graph (Binary Tree) Testfailed2.8failed1.7failed2.2
Multithreading Testfailed21.3failed5.0failed13.1
All Tests0.0128.30.976.60.497.5

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (7.5) reveals that in these tests, EclipseLink with Derby embedded is 15.3 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 Derby embedded database (7.3) reveals that in that case, EclipseLink with Derby embedded is 664 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 embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
Basic Person Test0.0114.61.54.70.744.6
Element Collection Test0.0102.51.61.40.801.9
Inheritance Test0.00933.91.14.50.574.2
Indexing Test0.0176.22.13.81.15.0
Graph (Binary Tree) Testfailed1.1failed1.0failed1.1
Multithreading Testfailed6.2failed5.8failed6.0
All Tests0.0124.11.63.50.793.8

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (3.8) reveals that in these tests, EclipseLink with Derby embedded 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.0093) to the normalized speed of EclipseLink with Derby embedded database (3.9) reveals that in that case, EclipseLink with Derby embedded is 419 times faster than DataNucleus with DB4O embedded.

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
Basic Person Test35.151.135.451.035.251.1
Element Collection Test29.538.529.939.429.738.9
Inheritance Test33.448.033.547.933.448.0
Indexing Test41.051.641.952.341.552.0
Graph (Binary Tree) Testfailed13.4failed11.7failed12.6
Multithreading Testfailed52.6failed8.4failed30.5
All Tests34.842.535.235.135.038.8

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

The results above show that in general EclipseLink with Derby embedded is slightly more efficient than DataNucleus with DB4O embedded in using disk space.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
DataNucleus
DB4O embedded
EclipseLink
Derby embedded
Basic Person Test0.02217.31.317.50.6817.4
Element Collection Test0.01811.31.35.40.668.3
Inheritance Test0.01914.01.218.20.6316.1
Indexing Test0.0288.41.927.20.9417.8
Graph (Binary Tree) Testfailed2.2failed2.6failed2.4
Multithreading Testfailed21.2failed13.9failed17.6
All Tests0.02212.71.414.50.7313.6

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

Other Head to Head DBMS/JPA Comparisons