Compare with

Comparison of EclipseLink with H2 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
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embedded
Basic Person Test5.61002.51004.0100
Element Collection Test4.21001.51002.8100
Inheritance Test6.61002.11004.4100
Indexing Test9.71004.11006.9100
Graph (Binary Tree) Test4.788.43.51004.194.2
Multithreading Test10.21004.01007.1100
All Tests6.898.12.91004.999.0

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
 EclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embedded
Basic Person Test5.51008.21006.8100
Element Collection Test3.21004.21003.7100
Inheritance Test4.710010.11007.4100
Indexing Test4.41009.41006.9100
Graph (Binary Tree) Test1.11001.91001.5100
Multithreading Test12.210015.910014.0100
All Tests5.21008.31006.7100

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
 EclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embedded
Basic Person Test3.81001.11002.5100
Element Collection Test4.11001.11002.6100
Inheritance Test3.21001.31002.3100
Indexing Test3.01008.01005.5100
Multithreading Test1.11001.01001.1100
All Tests3.01002.51002.8100

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
 EclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embedded
Basic Person Test4.51002.21003.4100
Element Collection Test3.81002.41003.1100
Inheritance Test4.41003.01003.7100
Indexing Test4.21003.11003.7100
Graph (Binary Tree) Test1.41000.791001.1100
Multithreading Test7.81002.51005.1100
All Tests4.31002.31003.3100

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
 EclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embedded
Basic Person Test6.41003.11004.8100
Element Collection Test3.01001.31002.2100
Inheritance Test5.61002.81004.2100
Indexing Test10.31003.81007.0100
Graph (Binary Tree) Test1.51001.31001.4100
Multithreading Test7.01004.91006.0100
All Tests5.61002.91004.3100

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
 EclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embeddedEclipseLink
H2 server
ObjectDB embedded
Basic Person Test5.21003.41004.3100
Element Collection Test3.61002.11002.9100
Inheritance Test4.91003.91004.4100
Indexing Test6.31005.71006.0100
Graph (Binary Tree) Test2.197.11.91002.098.5
Multithreading Test7.71005.71006.7100
All Tests5.199.63.81004.599.8

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