Compare with

Comparison of EclipseLink with Derby server 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 server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embedded
Basic Person Test3.81003.11003.4100
Element Collection Test2.21001.51001.8100
Inheritance Test3.91002.91003.4100
Indexing Test5.21004.31004.7100
Graph (Binary Tree) Test1.988.41.71001.894.2
Multithreading Test6.11003.91005.0100
All Tests3.898.12.91003.499.0

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embedded
Basic Person Test6.410011.31008.8100
Element Collection Test1.81002.41002.1100
Inheritance Test3.710012.91008.3100
Indexing Test3.610012.81008.2100
Graph (Binary Tree) Test0.611000.731000.67100
Multithreading Test8.510019.810014.1100
All Tests4.110010.01007.0100

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embedded
Basic Person Test45.81005.310025.6100
Element Collection Test35.21000.9910018.1100
Inheritance Test23.11005.910014.5100
Indexing Test2.510012.21007.4100
Multithreading Test34.31007.710021.0100
All Tests28.21006.410017.3100

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embedded
Basic Person Test3.91004.41004.1100
Element Collection Test1.71001.61001.6100
Inheritance Test4.61006.11005.3100
Indexing Test4.51007.61006.1100
Graph (Binary Tree) Test0.701000.421000.56100
Multithreading Test7.31004.81006.0100
All Tests3.81004.21004.0100

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embedded
Basic Person Test2.81003.91003.3100
Element Collection Test1.21000.551000.87100
Inheritance Test3.31003.71003.5100
Indexing Test4.91003.51004.2100
Graph (Binary Tree) Test0.511000.501000.51100
Multithreading Test4.81005.71005.3100
All Tests2.91003.01003.0100

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embeddedEclipseLink
Derby server
ObjectDB embedded
Basic Person Test12.51005.61009.1100
Element Collection Test8.41001.41004.9100
Inheritance Test7.71006.31007.0100
Indexing Test4.11008.11006.1100
Graph (Binary Tree) Test0.9397.10.831000.8898.5
Multithreading Test12.21008.410010.3100
All Tests7.999.65.21006.699.8

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

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

Other Head to Head DBMS/JPA Comparisons