Compare with

Comparison of ObjectDB embedded vs EclipseLink with H2 server

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 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
Basic Person Test1005.61002.51004.0
Element Collection Test1004.21001.51002.8
Inheritance Test1006.61002.11004.4
Indexing Test1009.71004.11006.9
Graph (Binary Tree) Test88.44.71003.594.24.1
Multithreading Test10010.21004.01007.1
All Tests98.16.81002.999.04.9

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

A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with H2 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 H2 server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
Basic Person Test1005.51008.21006.8
Element Collection Test1003.21004.21003.7
Inheritance Test1004.710010.11007.4
Indexing Test1004.41009.41006.9
Graph (Binary Tree) Test1001.11001.91001.5
Multithreading Test10012.210015.910014.0
All Tests1005.21008.31006.7

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
Basic Person Test1003.81001.11002.5
Element Collection Test1004.11001.11002.6
Inheritance Test1003.21001.31002.3
Indexing Test1003.01008.01005.5
Multithreading Test1001.11001.01001.1
All Tests1003.01002.51002.8

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

A huge performance gap has been detected when using multithreading with large retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (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 H2 server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
Basic Person Test1004.51002.21003.4
Element Collection Test1003.81002.41003.1
Inheritance Test1004.41003.01003.7
Indexing Test1004.21003.11003.7
Graph (Binary Tree) Test1001.41000.791001.1
Multithreading Test1007.81002.51005.1
All Tests1004.31002.31003.3

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
Basic Person Test1006.41003.11004.8
Element Collection Test1003.01001.31002.2
Inheritance Test1005.61002.81004.2
Indexing Test10010.31003.81007.0
Graph (Binary Tree) Test1001.51001.31001.4
Multithreading Test1007.01004.91006.0
All Tests1005.61002.91004.3

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
Basic Person Test1005.21003.41004.3
Element Collection Test1003.61002.11002.9
Inheritance Test1004.91003.91004.4
Indexing Test1006.31005.71006.0
Graph (Binary Tree) Test97.12.11001.998.52.0
Multithreading Test1007.71005.71006.7
All Tests99.65.11003.899.84.5

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with H2 server in performing JPA database operations. Comparing the normalized speed of EclipseLink with H2 database server (4.5) to the normalized speed of ObjectDB embedded database (99.8) reveals that in these tests, ObjectDB embedded is 22.2 times faster than EclipseLink with H2 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 H2 database server (1.9) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 52.6 times faster than EclipseLink with H2 server.

Other Head to Head DBMS/JPA Comparisons