Compare with

Comparison of ObjectDB embedded vs DataNucleus with MySQL 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
 ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
Basic Person Test1002.61001.41002.0
Element Collection Test1001.01000.481000.76
Inheritance Test1002.51001.31001.9
Indexing Test1004.01002.51003.3
Graph (Binary Tree) Test88.41.11000.9994.21.1
Multithreading Test1006.21002.51004.4
All Tests98.12.91001.599.02.2

The results above show that in general ObjectDB 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 ObjectDB embedded database (99.0) reveals that in these tests, ObjectDB embedded is 45.0 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (0.48) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 208 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
 ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
Basic Person Test1000.961009.31005.1
Element Collection Test1000.181000.771000.47
Inheritance Test1000.551008.51004.5
Indexing Test1000.821009.71005.3
Graph (Binary Tree) Test1002.11003.51002.8
Multithreading Test1000.271007.81004.0
All Tests1000.811006.61003.7

The results above show that in general ObjectDB embedded is much 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 ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 27.0 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.18) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 556 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
 ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
Basic Person Test1007.21002.21004.7
Element Collection Test1005.81000.271003.1
Inheritance Test1002.91001.71002.3
Indexing Test1000.00841002.51001.2
Multithreading Test100failed100failed100failed
All Tests1004.01001.71002.8

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

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
Basic Person Test1000.611001.11000.88
Element Collection Test1000.311000.441000.38
Inheritance Test1000.511001.81001.1
Indexing Test1000.681002.21001.5
Graph (Binary Tree) Test1000.911000.471000.69
Multithreading Test1000.64100failed1000.64
All Tests1000.611001.21000.88

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

The results above show that in general ObjectDB 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 ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 114 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 ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 323 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
 ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
Basic Person Test1000.701001.31001.0
Element Collection Test1000.171000.401000.29
Inheritance Test1000.411001.31000.87
Indexing Test1001.71001.91001.8
Graph (Binary Tree) Test1000.491000.461000.47
Multithreading Test100failed100failed100failed
All Tests1000.691001.11000.89

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

The results above show that in general ObjectDB 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 ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 112 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 ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 588 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
 ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
ObjectDB embeddedDataNucleus
MySQL server
Basic Person Test1002.41003.11002.7
Element Collection Test1001.51000.471000.99
Inheritance Test1001.41002.91002.1
Indexing Test1001.41003.81002.6
Graph (Binary Tree) Test97.11.21001.498.51.3
Multithreading Test1002.41005.11003.5
All Tests99.61.71002.699.82.1

The results above show that in general ObjectDB 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 ObjectDB embedded database (99.8) reveals that in these tests, ObjectDB embedded is 47.5 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.47) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 213 times faster than DataNucleus with MySQL server.

Other Head to Head DBMS/JPA Comparisons