Compare with

Comparison of EclipseLink with PostgreSQL server vs ObjectDB 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
 EclipseLink
PostgreSQL server
ObjectDB serverEclipseLink
PostgreSQL server
ObjectDB serverEclipseLink
PostgreSQL server
ObjectDB server
Basic Person Test7.335.24.274.15.854.7
Element Collection Test3.138.21.957.82.548.0
Inheritance Test6.932.75.072.85.952.7
Indexing Test10.049.96.890.18.470.0
Graph (Binary Tree) Test3.51003.389.23.494.6
Multithreading Test31.876.614.599.423.188.0
All Tests10.455.46.080.68.268.0

The results above show that in general ObjectDB server 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 database server (68.0) reveals that in these tests, ObjectDB server is 8.3 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 database server (57.8) reveals that in that case, ObjectDB server is 30.4 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 serverEclipseLink
PostgreSQL server
ObjectDB serverEclipseLink
PostgreSQL server
ObjectDB server
Basic Person Test6.815.717.245.412.030.5
Element Collection Test0.02619.90.02049.20.02334.6
Inheritance Test6.013.219.749.412.931.3
Indexing Test5.614.019.559.512.636.8
Graph (Binary Tree) Test0.4719.90.6124.70.5422.3
Multithreading Test13.519.727.860.220.640.0
All Tests5.417.114.148.19.832.6

The results above show that in general ObjectDB server 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 database server (32.6) reveals that in these tests, ObjectDB server is 3.3 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 database server (49.2) reveals that in that case, ObjectDB server is 2,460 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 serverEclipseLink
PostgreSQL server
ObjectDB serverEclipseLink
PostgreSQL server
ObjectDB server
Basic Person Test55.538.87.825.931.632.4
Element Collection Test15.439.50.02833.17.736.3
Inheritance Test54.934.811.534.033.234.4
Indexing Test0.07714.510.053.35.133.9
Multithreading Test55.350.812.052.133.751.5
All Tests36.235.78.339.722.337.7

The results above show that in general ObjectDB server is more efficient than EclipseLink with PostgreSQL server in executing the tested JPA queries.

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 database server (33.1) reveals that in that case, ObjectDB server is 1,182 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 serverEclipseLink
PostgreSQL server
ObjectDB serverEclipseLink
PostgreSQL server
ObjectDB server
Basic Person Test6.218.34.140.95.129.6
Element Collection Test0.08021.10.02853.70.05437.4
Inheritance Test6.419.96.151.96.235.9
Indexing Test6.517.97.052.16.835.0
Graph (Binary Tree) Test0.9042.60.5024.10.7033.3
Multithreading Test36.068.69.168.722.568.6
All Tests9.331.44.548.66.940.0

The results above show that in general ObjectDB server 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 database server (40.0) reveals that in these tests, ObjectDB server is 5.8 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 database server (53.7) reveals that in that case, ObjectDB server is 1,918 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 serverEclipseLink
PostgreSQL server
ObjectDB serverEclipseLink
PostgreSQL server
ObjectDB server
Basic Person Test5.720.25.767.75.744.0
Element Collection Test0.02522.9stopped57.60.01240.2
Inheritance Test5.523.15.461.65.442.3
Indexing Test10.434.910.055.910.245.4
Graph (Binary Tree) Test0.01619.30.01327.90.01523.6
Multithreading Test26.338.516.850.521.644.5
All Tests8.026.56.353.57.240.0

The results above show that in general ObjectDB server 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 database server (40.0) reveals that in these tests, ObjectDB server is 5.6 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 database server (27.9) reveals that in that case, ObjectDB server is 2,146 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 serverEclipseLink
PostgreSQL server
ObjectDB serverEclipseLink
PostgreSQL server
ObjectDB server
Basic Person Test16.325.67.850.812.138.2
Element Collection Test3.728.30.4050.32.139.3
Inheritance Test15.924.79.553.912.739.3
Indexing Test6.526.210.762.28.644.2
Graph (Binary Tree) Test1.245.41.141.51.243.5
Multithreading Test32.650.816.066.224.358.5
All Tests13.133.17.854.610.543.9

The results above show that in general ObjectDB server 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 database server (43.9) reveals that in these tests, ObjectDB server is 4.2 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 database server (50.3) reveals that in that case, ObjectDB server is 126 times faster than EclipseLink with PostgreSQL server.

Other Head to Head DBMS/JPA Comparisons