Compare with

Comparison of ObjectDB embedded vs EclipseLink with PostgreSQL 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
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
Basic Person Test1007.31004.21005.8
Element Collection Test1003.11001.91002.5
Inheritance Test1006.91005.01005.9
Indexing Test10010.01006.81008.4
Graph (Binary Tree) Test88.43.51003.394.23.4
Multithreading Test10031.810014.510023.1
All Tests98.110.41006.099.08.2

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
Basic Person Test1006.810017.210012.0
Element Collection Test1000.0261000.0201000.023
Inheritance Test1006.010019.710012.9
Indexing Test1005.610019.510012.6
Graph (Binary Tree) Test1000.471000.611000.54
Multithreading Test10013.510027.810020.6
All Tests1005.410014.11009.8

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
Basic Person Test10055.51007.810031.6
Element Collection Test10015.41000.0281007.7
Inheritance Test10054.910011.510033.2
Indexing Test1000.07710010.01005.1
Multithreading Test10055.310012.010033.7
All Tests10036.21008.310022.3

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
Basic Person Test1006.21004.11005.1
Element Collection Test1000.0801000.0281000.054
Inheritance Test1006.41006.11006.2
Indexing Test1006.51007.01006.8
Graph (Binary Tree) Test1000.901000.501000.70
Multithreading Test10036.01009.110022.5
All Tests1009.31004.51006.9

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with PostgreSQL server in updating JPA entity objects in the database. Comparing the normalized speed of EclipseLink with PostgreSQL database server (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 PostgreSQL server.

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
Basic Person Test1005.71005.71005.7
Element Collection Test1000.025100stopped1000.012
Inheritance Test1005.51005.41005.4
Indexing Test10010.410010.010010.2
Graph (Binary Tree) Test1000.0161000.0131000.015
Multithreading Test10026.310016.810021.6
All Tests1008.01006.31007.2

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
Basic Person Test10016.31007.810012.1
Element Collection Test1003.71000.401002.1
Inheritance Test10015.91009.510012.7
Indexing Test1006.510010.71008.6
Graph (Binary Tree) Test97.11.21001.198.51.2
Multithreading Test10032.610016.010024.3
All Tests99.613.11007.899.810.5

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

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

Other Head to Head DBMS/JPA Comparisons