Compare with

Comparison of ObjectDB embedded vs EclipseLink with H2 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 embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
Basic Person Test10025.11008.910017.0
Element Collection Test10020.41008.010014.2
Inheritance Test10028.71008.710018.7
Indexing Test10037.610014.010025.8
Graph (Binary Tree) Test88.417.710014.794.216.2
Multithreading Test10030.310011.410020.8
All Tests98.126.610010.999.018.8

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
 ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
Basic Person Test10030.410029.110029.7
Element Collection Test10019.610027.610023.6
Inheritance Test10033.810039.810036.8
Indexing Test10022.210041.310031.8
Graph (Binary Tree) Test10016.010020.010018.0
Multithreading Test10033.710029.010031.4
All Tests10025.910031.110028.5

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
 ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
Basic Person Test1004.41001.41002.9
Element Collection Test1004.11002.41003.2
Inheritance Test1003.41002.01002.7
Indexing Test10013.010022.810017.9
Multithreading Test1001.01000.671000.85
All Tests1005.21005.91005.5

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
 ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
Basic Person Test10016.61007.610012.1
Element Collection Test10015.310010.510012.9
Inheritance Test10015.71009.810012.7
Indexing Test10012.11009.910011.0
Graph (Binary Tree) Test10013.71007.010010.3
Multithreading Test10020.91004.210012.6
All Tests10015.71008.210012.0

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
 ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
Basic Person Test10035.110019.610027.4
Element Collection Test10019.31008.510013.9
Inheritance Test10036.010014.010025.0
Indexing Test10042.510019.210030.9
Graph (Binary Tree) Test10012.210014.410013.3
Multithreading Test10054.410025.810040.1
All Tests10033.310016.910025.1

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
 ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
Basic Person Test10036.210039.210037.7
Element Collection Test10033.310034.910034.1
Inheritance Test10035.410036.210035.8
Indexing Test10039.810043.710041.7
Graph (Binary Tree) Test10041.010028.410034.7
Multithreading Test91.148.722.012.456.630.6
All Tests98.539.187.032.592.835.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
 ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
ObjectDB embeddedEclipseLink
H2 embedded
Basic Person Test10022.310013.310017.8
Element Collection Test10015.710011.410013.6
Inheritance Test10023.510014.910019.2
Indexing Test10025.510021.510023.5
Graph (Binary Tree) Test97.114.910014.098.514.5
Multithreading Test10028.110014.210021.1
All Tests99.621.910014.999.818.4

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