Compare with

Comparison of DataNucleus with MySQL server vs DataNucleus 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
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
Basic Person Test2.614.21.44.82.09.5
Element Collection Test1.06.60.482.10.764.3
Inheritance Test2.513.61.34.61.99.1
Indexing Test4.024.62.511.13.317.8
Graph (Binary Tree) Test1.16.80.994.51.15.7
Multithreading Test6.238.52.58.54.423.5
All Tests2.917.41.55.92.211.7

The results above show that in general DataNucleus with HSQLDB embedded is much more efficient than DataNucleus with MySQL server in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with MySQL database server (2.2) to the normalized speed of DataNucleus with HSQLDB embedded database (11.7) reveals that in these tests, DataNucleus with HSQLDB embedded is 5.3 times faster than DataNucleus with MySQL server.

A large performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (1.0) to the normalized speed of DataNucleus with HSQLDB embedded database (6.6) reveals that in that case, DataNucleus with HSQLDB embedded is 6.6 times faster than DataNucleus with MySQL server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
Basic Person Test0.966.69.310.25.18.4
Element Collection Test0.183.60.778.10.475.8
Inheritance Test0.555.78.58.84.57.2
Indexing Test0.825.19.79.55.37.3
Graph (Binary Tree) Test2.17.23.59.32.88.3
Multithreading Test0.278.17.89.54.08.8
All Tests0.816.06.69.23.77.6

The results above show that in general DataNucleus with HSQLDB embedded is more efficient than DataNucleus with MySQL server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with MySQL database server (3.7) to the normalized speed of DataNucleus with HSQLDB embedded database (7.6) reveals that in these tests, DataNucleus with HSQLDB embedded is 2.1 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.27) to the normalized speed of DataNucleus with HSQLDB embedded database (8.1) reveals that in that case, DataNucleus with HSQLDB embedded is 30.0 times faster than DataNucleus with MySQL server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
Basic Person Test7.21.42.20.484.70.95
Element Collection Test5.81.30.270.673.11.0
Inheritance Test2.91.61.70.612.31.1
Indexing Test0.00840.00162.50.631.20.32
Multithreading Testfailed0.40failedfailedfailed0.40
All Tests4.00.961.70.602.80.80

DataNucleus with MySQL server has failed in 2 tests (see exceptions). DataNucleus with HSQLDB embedded has failed in 1 tests (see exceptions).

The results above show that in general DataNucleus with MySQL server is much more efficient than DataNucleus with HSQLDB embedded in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with HSQLDB embedded database (0.80) to the normalized speed of DataNucleus with MySQL database server (2.8) reveals that in these tests, DataNucleus with MySQL server is 3.5 times faster than DataNucleus with HSQLDB embedded.

A large performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with HSQLDB embedded database (0.0016) to the normalized speed of DataNucleus with MySQL database server (0.0084) reveals that in that case, DataNucleus with MySQL server is 5.2 times faster than DataNucleus with HSQLDB embedded.

On the other hand, DataNucleus with MySQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.27) to the normalized speed of DataNucleus with HSQLDB embedded database (0.67) reveals that in that case, DataNucleus with MySQL server is 2.5 times slower than DataNucleus with HSQLDB embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
Basic Person Test0.6111.51.12.70.887.1
Element Collection Test0.316.90.442.70.384.8
Inheritance Test0.5110.31.83.61.16.9
Indexing Test0.6811.42.24.41.57.9
Graph (Binary Tree) Test0.913.50.471.50.692.5
Multithreading Test0.64failedfailedfailed0.64failed
All Tests0.618.71.23.00.885.8

DataNucleus with MySQL server has failed in 1 tests (see exceptions). DataNucleus with HSQLDB embedded has failed in 2 tests (see exceptions).

The results above show that in general DataNucleus with HSQLDB embedded is much more efficient than DataNucleus with MySQL server in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with MySQL database server (0.88) to the normalized speed of DataNucleus with HSQLDB embedded database (5.8) reveals that in these tests, DataNucleus with HSQLDB embedded is 6.6 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (0.31) to the normalized speed of DataNucleus with HSQLDB embedded database (6.9) reveals that in that case, DataNucleus with HSQLDB embedded is 22.3 times faster than DataNucleus with MySQL server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
Basic Person Test0.704.21.31.31.02.8
Element Collection Test0.174.90.401.60.293.2
Inheritance Test0.414.01.31.30.872.7
Indexing Test1.77.51.91.91.84.7
Graph (Binary Tree) Test0.492.90.462.00.472.5
Multithreading Testfailed40.1failed13.7failed26.9
All Tests0.6910.61.13.70.897.1

DataNucleus with MySQL server has failed in 2 tests (see exceptions).

The results above show that in general DataNucleus with HSQLDB embedded is much more efficient than DataNucleus with MySQL server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with MySQL database server (0.89) to the normalized speed of DataNucleus with HSQLDB embedded database (7.1) reveals that in these tests, DataNucleus with HSQLDB embedded is 8.0 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (0.17) to the normalized speed of DataNucleus with HSQLDB embedded database (4.9) reveals that in that case, DataNucleus with HSQLDB embedded is 28.8 times faster than DataNucleus with MySQL server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
DataNucleus
MySQL server
DataNucleus
HSQLDB embedded
Basic Person Test2.47.63.13.92.75.7
Element Collection Test1.54.70.473.00.993.8
Inheritance Test1.47.12.93.82.15.4
Indexing Test1.49.73.85.52.67.6
Graph (Binary Tree) Test1.25.11.44.31.34.7
Multithreading Test2.421.85.110.63.517.0
All Tests1.79.02.64.82.17.0

The results above show that in general DataNucleus with HSQLDB embedded is much more efficient than DataNucleus with MySQL server in performing JPA database operations. Comparing the normalized speed of DataNucleus with MySQL database server (2.1) to the normalized speed of DataNucleus with HSQLDB embedded database (7.0) reveals that in these tests, DataNucleus with HSQLDB embedded is 3.3 times faster than DataNucleus with MySQL server.

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (2.4) to the normalized speed of DataNucleus with HSQLDB embedded database (21.8) reveals that in that case, DataNucleus with HSQLDB embedded is 9.1 times faster than DataNucleus with MySQL server.

Other Head to Head DBMS/JPA Comparisons