Compare with

Comparison of EclipseLink with PostgreSQL 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
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embedded
Basic Person Test7.31004.21005.8100
Element Collection Test3.11001.91002.5100
Inheritance Test6.91005.01005.9100
Indexing Test10.01006.81008.4100
Graph (Binary Tree) Test3.588.43.31003.494.2
Multithreading Test31.810014.510023.1100
All Tests10.498.16.01008.299.0

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
 EclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embedded
Basic Person Test6.810017.210012.0100
Element Collection Test0.0261000.0201000.023100
Inheritance Test6.010019.710012.9100
Indexing Test5.610019.510012.6100
Graph (Binary Tree) Test0.471000.611000.54100
Multithreading Test13.510027.810020.6100
All Tests5.410014.11009.8100

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
 EclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embedded
Basic Person Test55.51007.810031.6100
Element Collection Test15.41000.0281007.7100
Inheritance Test54.910011.510033.2100
Indexing Test0.07710010.01005.1100
Multithreading Test55.310012.010033.7100
All Tests36.21008.310022.3100

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
 EclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embedded
Basic Person Test6.21004.11005.1100
Element Collection Test0.0801000.0281000.054100
Inheritance Test6.41006.11006.2100
Indexing Test6.51007.01006.8100
Graph (Binary Tree) Test0.901000.501000.70100
Multithreading Test36.01009.110022.5100
All Tests9.31004.51006.9100

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
 EclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embedded
Basic Person Test5.71005.71005.7100
Element Collection Test0.025100stopped1000.012100
Inheritance Test5.51005.41005.4100
Indexing Test10.410010.010010.2100
Graph (Binary Tree) Test0.0161000.0131000.015100
Multithreading Test26.310016.810021.6100
All Tests8.01006.31007.2100

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
 EclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embeddedEclipseLink
PostgreSQL server
ObjectDB embedded
Basic Person Test16.31007.810012.1100
Element Collection Test3.71000.401002.1100
Inheritance Test15.91009.510012.7100
Indexing Test6.510010.71008.6100
Graph (Binary Tree) Test1.297.11.11001.298.5
Multithreading Test32.610016.010024.3100
All Tests13.199.67.810010.599.8

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