Compare with

Comparison of EclipseLink with H2 embedded vs DataNucleus with DB4O 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
 EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test25.10.0598.91.317.00.69
Element Collection Test20.40.0458.01.014.20.52
Inheritance Test28.70.0518.70.8518.70.45
Indexing Test37.60.08014.02.325.81.2
Graph (Binary Tree) Test17.7failed14.7failed16.2failed
Multithreading Test30.3failed11.4failed20.8failed
All Tests26.60.05910.91.418.80.71

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

The results above show that in general EclipseLink with H2 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 H2 embedded database (18.8) reveals that in these tests, EclipseLink with H2 embedded is 26.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 H2 embedded database (28.7) reveals that in that case, EclipseLink with H2 embedded is 563 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
 EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test30.40.004729.11.829.70.90
Element Collection Test19.60.003827.61.523.60.77
Inheritance Test33.80.003539.82.236.81.1
Indexing Test22.20.004341.31.831.80.89
Graph (Binary Tree) Test16.0failed20.0failed18.0failed
Multithreading Test33.7failed29.0failed31.4failed
All Tests25.90.004131.11.828.50.91

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

The results above show that in general EclipseLink with H2 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 H2 embedded database (28.5) reveals that in these tests, EclipseLink with H2 embedded is 31.3 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 H2 embedded database (33.8) reveals that in that case, EclipseLink with H2 embedded is 9,657 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
 EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test4.4failed1.4failed2.9failed
Element Collection Test4.1failed2.4failed3.2failed
Inheritance Test3.4failed2.0failed2.7failed
Indexing Test13.0failed22.8failed17.9failed
Multithreading Test1.0failed0.67failed0.85failed
All Tests5.2failed5.9failed5.5failed

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
 EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test16.60.0127.60.7612.10.39
Element Collection Test15.30.01210.51.112.90.53
Inheritance Test15.70.0119.80.8112.70.41
Indexing Test12.10.0119.91.311.00.64
Graph (Binary Tree) Test13.7failed7.0failed10.3failed
Multithreading Test20.9failed4.2failed12.6failed
All Tests15.70.0128.20.9712.00.49

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

The results above show that in general EclipseLink with H2 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 H2 embedded database (12.0) reveals that in these tests, EclipseLink with H2 embedded is 24.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.011) to the normalized speed of EclipseLink with H2 embedded database (15.7) reveals that in that case, EclipseLink with H2 embedded is 1,427 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
 EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test35.10.01119.61.527.40.74
Element Collection Test19.30.0108.51.613.90.80
Inheritance Test36.00.009314.01.125.00.57
Indexing Test42.50.01719.22.130.91.1
Graph (Binary Tree) Test12.2failed14.4failed13.3failed
Multithreading Test54.4failed25.8failed40.1failed
All Tests33.30.01216.91.625.10.79

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

The results above show that in general EclipseLink with H2 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 H2 embedded database (25.1) reveals that in these tests, EclipseLink with H2 embedded is 31.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 H2 embedded database (36.0) reveals that in that case, EclipseLink with H2 embedded is 3,871 times faster than DataNucleus with DB4O embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test36.235.139.235.437.735.2
Element Collection Test33.329.534.929.934.129.7
Inheritance Test35.433.436.233.535.833.4
Indexing Test39.841.043.741.941.741.5
Graph (Binary Tree) Test41.0failed28.4failed34.7failed
Multithreading Test48.7failed12.4failed30.6failed
All Tests39.134.832.535.235.835.0

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

The results above show that in general EclipseLink with H2 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
 EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
EclipseLink
H2 embedded
DataNucleus
DB4O embedded
Basic Person Test22.30.02213.31.317.80.68
Element Collection Test15.70.01811.41.313.60.66
Inheritance Test23.50.01914.91.219.20.63
Indexing Test25.50.02821.51.923.50.94
Graph (Binary Tree) Test14.9failed14.0failed14.5failed
Multithreading Test28.1failed14.2failed21.1failed
All Tests21.90.02214.91.418.40.73

The results above show that in general EclipseLink with H2 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 H2 embedded database (18.4) reveals that in these tests, EclipseLink with H2 embedded is 25.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/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.019) to the normalized speed of EclipseLink with H2 embedded database (23.5) reveals that in that case, EclipseLink with H2 embedded is 1,237 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons