Compare with

Comparison of ObjectDB server 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
 ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
Basic Person Test35.20.05974.11.354.70.69
Element Collection Test38.20.04557.81.048.00.52
Inheritance Test32.70.05172.80.8552.70.45
Indexing Test49.90.08090.12.370.01.2
Graph (Binary Tree) Test100failed89.2failed94.6failed
Multithreading Test76.6failed99.4failed88.0failed
All Tests55.40.05980.61.468.00.71

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

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.045) to the normalized speed of ObjectDB database server (38.2) reveals that in that case, ObjectDB server is 849 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
 ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
Basic Person Test15.70.004745.41.830.50.90
Element Collection Test19.90.003849.21.534.60.77
Inheritance Test13.20.003549.42.231.31.1
Indexing Test14.00.004359.51.836.80.89
Graph (Binary Tree) Test19.9failed24.7failed22.3failed
Multithreading Test19.7failed60.2failed40.0failed
All Tests17.10.004148.11.832.60.91

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

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

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0038) to the normalized speed of ObjectDB database server (19.9) reveals that in that case, ObjectDB server is 5,237 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
 ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
Basic Person Test38.8failed25.9failed32.4failed
Element Collection Test39.5failed33.1failed36.3failed
Inheritance Test34.8failed34.0failed34.4failed
Indexing Test14.5failed53.3failed33.9failed
Multithreading Test50.8failed52.1failed51.5failed
All Tests35.7failed39.7failed37.7failed

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
 ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
Basic Person Test18.30.01240.90.7629.60.39
Element Collection Test21.10.01253.71.137.40.53
Inheritance Test19.90.01151.90.8135.90.41
Indexing Test17.90.01152.11.335.00.64
Graph (Binary Tree) Test42.6failed24.1failed33.3failed
Multithreading Test68.6failed68.7failed68.6failed
All Tests31.40.01248.60.9740.00.49

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

The results above show that in general ObjectDB server 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 ObjectDB database server (40.0) reveals that in these tests, ObjectDB server is 81.6 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 ObjectDB database server (19.9) reveals that in that case, ObjectDB server is 1,809 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
 ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
Basic Person Test20.20.01167.71.544.00.74
Element Collection Test22.90.01057.61.640.20.80
Inheritance Test23.10.009361.61.142.30.57
Indexing Test34.90.01755.92.145.41.1
Graph (Binary Tree) Test19.3failed27.9failed23.6failed
Multithreading Test38.5failed50.5failed44.5failed
All Tests26.50.01253.51.640.00.79

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

The results above show that in general ObjectDB server 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 ObjectDB database server (40.0) reveals that in these tests, ObjectDB server is 50.6 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 ObjectDB database server (23.1) reveals that in that case, ObjectDB server is 2,484 times faster than DataNucleus with DB4O embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
ObjectDB serverDataNucleus
DB4O embedded
Basic Person Test25.60.02250.81.338.20.68
Element Collection Test28.30.01850.31.339.30.66
Inheritance Test24.70.01953.91.239.30.63
Indexing Test26.20.02862.21.944.20.94
Graph (Binary Tree) Test45.4failed41.5failed43.5failed
Multithreading Test50.8failed66.2failed58.5failed
All Tests33.10.02254.61.443.90.73

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

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.018) to the normalized speed of ObjectDB database server (28.3) reveals that in that case, ObjectDB server is 1,572 times faster than DataNucleus with DB4O embedded.

Other Head to Head DBMS/JPA Comparisons