Compare with

Comparison of EclipseLink with Derby embedded vs ObjectDB 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
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embedded
Basic Person Test5.51003.71004.6100
Element Collection Test3.01001.71002.4100
Inheritance Test5.31003.51004.4100
Indexing Test6.91004.61005.8100
Graph (Binary Tree) Test2.088.41.91001.994.2
Multithreading Test9.31004.11006.7100
All Tests5.398.13.21004.399.0

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with Derby embedded in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with Derby embedded database (4.3) to the normalized speed of ObjectDB embedded database (99.0) reveals that in these tests, ObjectDB embedded is 23.0 times faster than EclipseLink with Derby embedded.

A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (1.7) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 58.8 times faster than EclipseLink with Derby embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embedded
Basic Person Test16.410058.710037.5100
Element Collection Test7.510013.310010.4100
Inheritance Test17.110058.910038.0100
Indexing Test14.210067.410040.8100
Graph (Binary Tree) Test2.81005.71004.2100
Multithreading Test28.010048.710038.4100
All Tests14.310042.110028.2100

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with Derby embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of EclipseLink with Derby embedded database (28.2) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 3.5 times faster than EclipseLink with Derby embedded.

A huge performance gap has been detected when using graphs of objects with small retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (2.8) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 35.7 times faster than EclipseLink with Derby embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embedded
Basic Person Test53.410013.810033.6100
Element Collection Test37.91004.410021.2100
Inheritance Test37.410015.010026.2100
Indexing Test7.610049.310028.4100
Multithreading Test41.21006.110023.6100
All Tests35.510017.710026.6100

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

A huge performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (4.4) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 22.7 times faster than EclipseLink with Derby embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embedded
Basic Person Test6.41006.71006.5100
Element Collection Test5.41006.21005.8100
Inheritance Test6.51009.21007.8100
Indexing Test7.310011.11009.2100
Graph (Binary Tree) Test2.81001.71002.2100
Multithreading Test21.31005.010013.1100
All Tests8.31006.61007.5100

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with Derby embedded in updating JPA entity objects in the database. Comparing the normalized speed of EclipseLink with Derby embedded database (7.5) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 13.3 times faster than EclipseLink with Derby embedded.

A huge performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (1.7) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 58.8 times faster than EclipseLink with Derby embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embedded
Basic Person Test4.61004.71004.6100
Element Collection Test2.51001.41001.9100
Inheritance Test3.91004.51004.2100
Indexing Test6.21003.81005.0100
Graph (Binary Tree) Test1.11001.01001.1100
Multithreading Test6.21005.81006.0100
All Tests4.11003.51003.8100

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with Derby embedded in deleting JPA entity objects from the database. Comparing the normalized speed of EclipseLink with Derby embedded database (3.8) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 26.3 times faster than EclipseLink with Derby embedded.

A huge performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (1.0) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 100 times faster than EclipseLink with Derby embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embedded
Basic Person Test51.110051.010051.1100
Element Collection Test38.510039.410038.9100
Inheritance Test48.010047.910048.0100
Indexing Test51.610052.310052.0100
Graph (Binary Tree) Test13.410011.710012.6100
Multithreading Test52.691.18.422.030.556.6
All Tests42.598.535.187.038.892.8

The results above show that in general ObjectDB embedded is more efficient than EclipseLink with Derby embedded in using disk space. Comparing the normalized score of EclipseLink with Derby embedded database (38.8) to the normalized score of ObjectDB embedded database (92.8) reveals that in these tests, ObjectDB embedded is 2.4 times more efficient than EclipseLink with Derby embedded.

A large gap has been detected when using graphs of objects with large transaction size. Comparing the normalized score of EclipseLink with Derby embedded database (11.7) to the normalized score of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 8.5 times more efficient than EclipseLink with Derby embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embeddedEclipseLink
Derby embedded
ObjectDB embedded
Basic Person Test17.310017.510017.4100
Element Collection Test11.31005.41008.3100
Inheritance Test14.010018.210016.1100
Indexing Test8.410027.210017.8100
Graph (Binary Tree) Test2.297.12.61002.498.5
Multithreading Test21.210013.910017.6100
All Tests12.799.614.510013.699.8

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with Derby embedded in performing JPA database operations. Comparing the normalized speed of EclipseLink with Derby embedded database (13.6) to the normalized speed of ObjectDB embedded database (99.8) reveals that in these tests, ObjectDB embedded is 7.3 times faster than EclipseLink with Derby embedded.

A huge performance gap has been detected when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (2.2) to the normalized speed of ObjectDB embedded database (97.1) reveals that in that case, ObjectDB embedded is 44.1 times faster than EclipseLink with Derby embedded.

Other Head to Head DBMS/JPA Comparisons