Compare with

Comparison of EclipseLink with HSQLDB 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
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embedded
Basic Person Test27.110017.210022.2100
Element Collection Test17.21008.210012.7100
Inheritance Test26.710011.910019.3100
Indexing Test30.610018.610024.6100
Graph (Binary Tree) Test20.088.415.910018.094.2
Multithreading Test32.510011.410022.0100
All Tests25.798.113.910019.899.0

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embedded
Basic Person Test24.410036.010030.2100
Element Collection Test14.910019.110017.0100
Inheritance Test22.810040.010031.4100
Indexing Test20.710038.710029.7100
Graph (Binary Tree) Test8.710014.210011.4100
Multithreading Test24.210028.010026.1100
All Tests19.310029.310024.3100

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embedded
Basic Person Test2.91000.881001.9100
Element Collection Test3.21001.41002.3100
Inheritance Test2.61001.11001.9100
Indexing Test21.510033.310027.4100
Multithreading Test1.11000.521000.82100
All Tests6.31007.41006.9100

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

A huge performance gap has been detected when using multithreading with large retrieval size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (0.52) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 192 times faster than EclipseLink with HSQLDB embedded.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embedded
Basic Person Test17.91007.010012.5100
Element Collection Test14.61008.310011.4100
Inheritance Test16.21009.710013.0100
Indexing Test12.01006.81009.4100
Graph (Binary Tree) Test4.71003.41004.0100
Multithreading Test24.41004.410014.4100
All Tests15.01006.610010.8100

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embedded
Basic Person Test32.310020.310026.3100
Element Collection Test14.31006.010010.2100
Inheritance Test29.210023.910026.6100
Indexing Test55.310027.110041.2100
Graph (Binary Tree) Test6.810014.110010.4100
Multithreading Test52.910028.410040.6100
All Tests31.810020.010025.9100

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embedded
Basic Person Test41.410041.410041.4100
Element Collection Test46.910046.910046.9100
Inheritance Test41.410041.410041.4100
Indexing Test48.410049.210048.8100
Graph (Binary Tree) Test28.510021.410025.0100
Multithreading Test51.991.110.322.031.156.6
All Tests43.198.535.187.039.192.8

The results above show that in general ObjectDB embedded is more efficient than EclipseLink with HSQLDB embedded in using disk space. Comparing the normalized score of EclipseLink with HSQLDB embedded database (39.1) 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 HSQLDB embedded.

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embeddedEclipseLink
HSQLDB embedded
ObjectDB embedded
Basic Person Test20.910016.310018.6100
Element Collection Test12.81008.610010.7100
Inheritance Test19.510017.310018.4100
Indexing Test28.010024.910026.5100
Graph (Binary Tree) Test10.097.111.910011.098.5
Multithreading Test27.010014.610020.8100
All Tests20.199.615.710017.999.8

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

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

Other Head to Head DBMS/JPA Comparisons