Compare with

Comparison of EclipseLink with H2 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
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embedded
Basic Person Test25.11008.910017.0100
Element Collection Test20.41008.010014.2100
Inheritance Test28.71008.710018.7100
Indexing Test37.610014.010025.8100
Graph (Binary Tree) Test17.788.414.710016.294.2
Multithreading Test30.310011.410020.8100
All Tests26.698.110.910018.899.0

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embedded
Basic Person Test30.410029.110029.7100
Element Collection Test19.610027.610023.6100
Inheritance Test33.810039.810036.8100
Indexing Test22.210041.310031.8100
Graph (Binary Tree) Test16.010020.010018.0100
Multithreading Test33.710029.010031.4100
All Tests25.910031.110028.5100

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embedded
Basic Person Test4.41001.41002.9100
Element Collection Test4.11002.41003.2100
Inheritance Test3.41002.01002.7100
Indexing Test13.010022.810017.9100
Multithreading Test1.01000.671000.85100
All Tests5.21005.91005.5100

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embedded
Basic Person Test16.61007.610012.1100
Element Collection Test15.310010.510012.9100
Inheritance Test15.71009.810012.7100
Indexing Test12.11009.910011.0100
Graph (Binary Tree) Test13.71007.010010.3100
Multithreading Test20.91004.210012.6100
All Tests15.71008.210012.0100

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embedded
Basic Person Test35.110019.610027.4100
Element Collection Test19.31008.510013.9100
Inheritance Test36.010014.010025.0100
Indexing Test42.510019.210030.9100
Graph (Binary Tree) Test12.210014.410013.3100
Multithreading Test54.410025.810040.1100
All Tests33.310016.910025.1100

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embedded
Basic Person Test36.210039.210037.7100
Element Collection Test33.310034.910034.1100
Inheritance Test35.410036.210035.8100
Indexing Test39.810043.710041.7100
Graph (Binary Tree) Test41.010028.410034.7100
Multithreading Test48.791.112.422.030.656.6
All Tests39.198.532.587.035.892.8

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embedded
Basic Person Test22.310013.310017.8100
Element Collection Test15.710011.410013.6100
Inheritance Test23.510014.910019.2100
Indexing Test25.510021.510023.5100
Graph (Binary Tree) Test14.997.114.010014.598.5
Multithreading Test28.110014.210021.1100
All Tests21.999.614.910018.499.8

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

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

Other Head to Head DBMS/JPA Comparisons