Compare with

Comparison of DataNucleus with DB4O embedded vs EclipseLink with HSQLDB 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
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
Basic Person Test0.05927.11.317.20.6922.2
Element Collection Test0.04517.21.08.20.5212.7
Inheritance Test0.05126.70.8511.90.4519.3
Indexing Test0.08030.62.318.61.224.6
Graph (Binary Tree) Testfailed20.0failed15.9failed18.0
Multithreading Testfailed32.5failed11.4failed22.0
All Tests0.05925.71.413.90.7119.8

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (19.8) reveals that in these tests, EclipseLink with HSQLDB embedded is 27.9 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 HSQLDB embedded database (26.7) reveals that in that case, EclipseLink with HSQLDB embedded is 524 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
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
Basic Person Test0.004724.41.836.00.9030.2
Element Collection Test0.003814.91.519.10.7717.0
Inheritance Test0.003522.82.240.01.131.4
Indexing Test0.004320.71.838.70.8929.7
Graph (Binary Tree) Testfailed8.7failed14.2failed11.4
Multithreading Testfailed24.2failed28.0failed26.1
All Tests0.004119.31.829.30.9124.3

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (24.3) reveals that in these tests, EclipseLink with HSQLDB embedded is 26.7 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 HSQLDB embedded database (22.8) reveals that in that case, EclipseLink with HSQLDB embedded is 6,514 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
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
Basic Person Testfailed2.9failed0.88failed1.9
Element Collection Testfailed3.2failed1.4failed2.3
Inheritance Testfailed2.6failed1.1failed1.9
Indexing Testfailed21.5failed33.3failed27.4
Multithreading Testfailed1.1failed0.52failed0.82
All Testsfailed6.3failed7.4failed6.9

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
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
Basic Person Test0.01217.90.767.00.3912.5
Element Collection Test0.01214.61.18.30.5311.4
Inheritance Test0.01116.20.819.70.4113.0
Indexing Test0.01112.01.36.80.649.4
Graph (Binary Tree) Testfailed4.7failed3.4failed4.0
Multithreading Testfailed24.4failed4.4failed14.4
All Tests0.01215.00.976.60.4910.8

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

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

A huge performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.012) to the normalized speed of EclipseLink with HSQLDB embedded database (17.9) reveals that in that case, EclipseLink with HSQLDB embedded is 1,492 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
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
Basic Person Test0.01132.31.520.30.7426.3
Element Collection Test0.01014.31.66.00.8010.2
Inheritance Test0.009329.21.123.90.5726.6
Indexing Test0.01755.32.127.11.141.2
Graph (Binary Tree) Testfailed6.8failed14.1failed10.4
Multithreading Testfailed52.9failed28.4failed40.6
All Tests0.01231.81.620.00.7925.9

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (25.9) reveals that in these tests, EclipseLink with HSQLDB embedded is 32.8 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 HSQLDB embedded database (55.3) reveals that in that case, EclipseLink with HSQLDB embedded is 3,253 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
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
Basic Person Test35.141.435.441.435.241.4
Element Collection Test29.546.929.946.929.746.9
Inheritance Test33.441.433.541.433.441.4
Indexing Test41.048.441.949.241.548.8
Graph (Binary Tree) Testfailed28.5failed21.4failed25.0
Multithreading Testfailed51.9failed10.3failed31.1
All Tests34.843.135.235.135.039.1

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

The results above show that in general EclipseLink with HSQLDB 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
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
DataNucleus
DB4O embedded
EclipseLink
HSQLDB embedded
Basic Person Test0.02220.91.316.30.6818.6
Element Collection Test0.01812.81.38.60.6610.7
Inheritance Test0.01919.51.217.30.6318.4
Indexing Test0.02828.01.924.90.9426.5
Graph (Binary Tree) Testfailed10.0failed11.9failed11.0
Multithreading Testfailed27.0failed14.6failed20.8
All Tests0.02220.11.415.70.7317.9

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

Other Head to Head DBMS/JPA Comparisons