Compare with

Comparison of EclipseLink with PostgreSQL server vs OpenJPA 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
 EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
Basic Person Test7.35.24.24.85.85.0
Element Collection Test3.12.81.92.22.52.5
Inheritance Test6.94.65.03.25.93.9
Indexing Test10.07.46.86.98.47.1
Graph (Binary Tree) Test3.50.983.30.813.40.89
Multithreading Test31.823.414.59.123.116.2
All Tests10.47.46.04.58.25.9

The results above show that in general EclipseLink with PostgreSQL server is more efficient than OpenJPA with PostgreSQL server in persisting JPA entity objects to the database.

A large performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.81) to the normalized speed of EclipseLink with PostgreSQL database server (3.3) reveals that in that case, EclipseLink with PostgreSQL server is 4.1 times faster than OpenJPA with PostgreSQL server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
Basic Person Test6.85.817.216.112.010.9
Element Collection Test0.0260.0130.0208.70.0234.4
Inheritance Test6.05.219.717.612.911.4
Indexing Test5.64.819.518.712.611.8
Graph (Binary Tree) Test0.470.270.610.350.540.31
Multithreading Test13.511.927.823.320.617.6
All Tests5.44.714.114.19.89.4

The results above show that in general EclipseLink with PostgreSQL server is slightly more efficient than OpenJPA with PostgreSQL server in retrieving JPA entity objects from the database.

A large performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.013) to the normalized speed of EclipseLink with PostgreSQL database server (0.026) reveals that in that case, EclipseLink with PostgreSQL server is 2.0 times faster than OpenJPA with PostgreSQL server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, 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 OpenJPA with PostgreSQL database server (8.7) reveals that in that case, EclipseLink with PostgreSQL server is 435 times slower than OpenJPA with PostgreSQL server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
Basic Person Test55.5failed7.8failed31.6failed
Element Collection Test15.4failed0.028failed7.7failed
Inheritance Test54.9failed11.5failed33.2failed
Indexing Test0.077failed10.0failed5.1failed
Multithreading Test55.3failed12.0failed33.7failed
All Tests36.2failed8.3failed22.3failed

OpenJPA with PostgreSQL server has failed in 10 tests (see exceptions).

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
Basic Person Test6.24.94.13.95.14.4
Element Collection Test0.0800.0330.0284.60.0542.3
Inheritance Test6.44.86.14.96.24.9
Indexing Test6.55.17.06.06.85.6
Graph (Binary Tree) Test0.900.570.500.310.700.44
Multithreading Test36.022.29.17.422.514.8
All Tests9.36.34.54.56.95.4

The results above show that in general EclipseLink with PostgreSQL server is slightly more efficient than OpenJPA with PostgreSQL server in updating JPA entity objects in the database.

A large performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.033) to the normalized speed of EclipseLink with PostgreSQL database server (0.080) reveals that in that case, EclipseLink with PostgreSQL server is 2.4 times faster than OpenJPA with PostgreSQL server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, 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 OpenJPA with PostgreSQL database server (4.6) reveals that in that case, EclipseLink with PostgreSQL server is 164 times slower than OpenJPA with PostgreSQL server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
Basic Person Test5.74.65.75.35.75.0
Element Collection Test0.0250.032stopped2.80.0121.4
Inheritance Test5.54.35.44.65.44.4
Indexing Test10.48.010.07.110.27.5
Graph (Binary Tree) Test0.0160.530.0130.550.0150.54
Multithreading Test26.317.416.89.121.613.3
All Tests8.05.86.34.97.25.4

The results above show that in general EclipseLink with PostgreSQL server is more efficient than OpenJPA with PostgreSQL server in deleting JPA entity objects from the database.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, 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 OpenJPA with PostgreSQL database server (0.55) reveals that in that case, EclipseLink with PostgreSQL server is 42.3 times slower than OpenJPA with PostgreSQL server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
EclipseLink
PostgreSQL server
OpenJPA
PostgreSQL server
Basic Person Test16.35.17.87.512.16.3
Element Collection Test3.70.720.404.62.12.6
Inheritance Test15.94.79.57.612.76.2
Indexing Test6.56.310.79.78.68.0
Graph (Binary Tree) Test1.20.591.10.501.20.55
Multithreading Test32.618.716.012.224.315.5
All Tests13.16.07.87.010.56.5

The results above show that in general EclipseLink with PostgreSQL server is more efficient than OpenJPA with PostgreSQL server in performing JPA database operations.

A large performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.72) to the normalized speed of EclipseLink with PostgreSQL database server (3.7) reveals that in that case, EclipseLink with PostgreSQL server is 5.1 times faster than OpenJPA with PostgreSQL server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, 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 OpenJPA with PostgreSQL database server (4.6) reveals that in that case, EclipseLink with PostgreSQL server is 11.5 times slower than OpenJPA with PostgreSQL server.

Other Head to Head DBMS/JPA Comparisons