Comparison of OpenJPA with PostgreSQL server vs EclipseLink with Derby 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 Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | |
| Basic Person Test | 5.2 | 3.8 | 4.8 | 3.1 | 5.0 | 3.4 |
| Element Collection Test | 2.8 | 2.2 | 2.2 | 1.5 | 2.5 | 1.8 |
| Inheritance Test | 4.6 | 3.9 | 3.2 | 2.9 | 3.9 | 3.4 |
| Indexing Test | 7.4 | 5.2 | 6.9 | 4.3 | 7.1 | 4.7 |
| Graph (Binary Tree) Test | 0.98 | 1.9 | 0.81 | 1.7 | 0.89 | 1.8 |
| Multithreading Test | 23.4 | 6.1 | 9.1 | 3.9 | 16.2 | 5.0 |
| All Tests | 7.4 | 3.8 | 4.5 | 2.9 | 5.9 | 3.4 |
The results above show that in general OpenJPA with PostgreSQL server is more efficient than EclipseLink with Derby server in persisting JPA entity objects to the database.
A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby database server (6.1) to the normalized speed of OpenJPA with PostgreSQL database server (23.4) reveals that in that case, OpenJPA with PostgreSQL server is 3.8 times faster than EclipseLink with Derby server.
On the other hand, OpenJPA with PostgreSQL server is slower, for instance, 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 Derby database server (1.7) reveals that in that case, OpenJPA with PostgreSQL server is 2.1 times slower than EclipseLink with Derby server.
Speed comparison of JPA database retrieval operations (normalized score, higher is better)
| Retrieval Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | |
| Basic Person Test | 5.8 | 6.4 | 16.1 | 11.3 | 10.9 | 8.8 |
| Element Collection Test | 0.013 | 1.8 | 8.7 | 2.4 | 4.4 | 2.1 |
| Inheritance Test | 5.2 | 3.7 | 17.6 | 12.9 | 11.4 | 8.3 |
| Indexing Test | 4.8 | 3.6 | 18.7 | 12.8 | 11.8 | 8.2 |
| Graph (Binary Tree) Test | 0.27 | 0.61 | 0.35 | 0.73 | 0.31 | 0.67 |
| Multithreading Test | 11.9 | 8.5 | 23.3 | 19.8 | 17.6 | 14.1 |
| All Tests | 4.7 | 4.1 | 14.1 | 10.0 | 9.4 | 7.0 |
The results above show that in general OpenJPA with PostgreSQL server is more efficient than EclipseLink with Derby server in retrieving JPA entity objects from the database.
A large performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (2.4) to the normalized speed of OpenJPA with PostgreSQL database server (8.7) reveals that in that case, OpenJPA with PostgreSQL server is 3.6 times faster than EclipseLink with Derby server.
On the other hand, OpenJPA with PostgreSQL server is slower, for instance, 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 Derby database server (1.8) reveals that in that case, OpenJPA with PostgreSQL server is 138 times slower than EclipseLink with Derby server.
Speed comparison of JPA database query operations (normalized score, higher is better)
| Retrieval Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | |
| Basic Person Test | failed | 45.8 | failed | 5.3 | failed | 25.6 |
| Element Collection Test | failed | 35.2 | failed | 0.99 | failed | 18.1 |
| Inheritance Test | failed | 23.1 | failed | 5.9 | failed | 14.5 |
| Indexing Test | failed | 2.5 | failed | 12.2 | failed | 7.4 |
| Multithreading Test | failed | 34.3 | failed | 7.7 | failed | 21.0 |
| All Tests | failed | 28.2 | failed | 6.4 | failed | 17.3 |
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 Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | |
| Basic Person Test | 4.9 | 3.9 | 3.9 | 4.4 | 4.4 | 4.1 |
| Element Collection Test | 0.033 | 1.7 | 4.6 | 1.6 | 2.3 | 1.6 |
| Inheritance Test | 4.8 | 4.6 | 4.9 | 6.1 | 4.9 | 5.3 |
| Indexing Test | 5.1 | 4.5 | 6.0 | 7.6 | 5.6 | 6.1 |
| Graph (Binary Tree) Test | 0.57 | 0.70 | 0.31 | 0.42 | 0.44 | 0.56 |
| Multithreading Test | 22.2 | 7.3 | 7.4 | 4.8 | 14.8 | 6.0 |
| All Tests | 6.3 | 3.8 | 4.5 | 4.2 | 5.4 | 4.0 |
The results above show that in general OpenJPA with PostgreSQL server is more efficient than EclipseLink with Derby server in updating JPA entity objects in the database.
A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby database server (7.3) to the normalized speed of OpenJPA with PostgreSQL database server (22.2) reveals that in that case, OpenJPA with PostgreSQL server is 3.0 times faster than EclipseLink with Derby server.
On the other hand, OpenJPA with PostgreSQL server is slower, for instance, 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 Derby database server (1.7) reveals that in that case, OpenJPA with PostgreSQL server is 51.5 times slower than EclipseLink with Derby server.
Speed comparison of JPA database removal operations (normalized score, higher is better)
| Transaction Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | |
| Basic Person Test | 4.6 | 2.8 | 5.3 | 3.9 | 5.0 | 3.3 |
| Element Collection Test | 0.032 | 1.2 | 2.8 | 0.55 | 1.4 | 0.87 |
| Inheritance Test | 4.3 | 3.3 | 4.6 | 3.7 | 4.4 | 3.5 |
| Indexing Test | 8.0 | 4.9 | 7.1 | 3.5 | 7.5 | 4.2 |
| Graph (Binary Tree) Test | 0.53 | 0.51 | 0.55 | 0.50 | 0.54 | 0.51 |
| Multithreading Test | 17.4 | 4.8 | 9.1 | 5.7 | 13.3 | 5.3 |
| All Tests | 5.8 | 2.9 | 4.9 | 3.0 | 5.4 | 3.0 |
The results above show that in general OpenJPA with PostgreSQL server is more efficient than EclipseLink with Derby server in deleting JPA entity objects from the database.
A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with Derby database server (0.55) to the normalized speed of OpenJPA with PostgreSQL database server (2.8) reveals that in that case, OpenJPA with PostgreSQL server is 5.1 times faster than EclipseLink with Derby server.
On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.032) to the normalized speed of EclipseLink with Derby database server (1.2) reveals that in that case, OpenJPA with PostgreSQL server is 37.5 times slower than EclipseLink with Derby server.
Comparison of JPA/Database speed - the averages (normalized score, higher is better)
| Transaction/Retrieval Size | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | OpenJPA PostgreSQL server | EclipseLink Derby server | |
| Basic Person Test | 5.1 | 12.5 | 7.5 | 5.6 | 6.3 | 9.1 |
| Element Collection Test | 0.72 | 8.4 | 4.6 | 1.4 | 2.6 | 4.9 |
| Inheritance Test | 4.7 | 7.7 | 7.6 | 6.3 | 6.2 | 7.0 |
| Indexing Test | 6.3 | 4.1 | 9.7 | 8.1 | 8.0 | 6.1 |
| Graph (Binary Tree) Test | 0.59 | 0.93 | 0.50 | 0.83 | 0.55 | 0.88 |
| Multithreading Test | 18.7 | 12.2 | 12.2 | 8.4 | 15.5 | 10.3 |
| All Tests | 6.0 | 7.9 | 7.0 | 5.2 | 6.5 | 6.6 |
The results above show that in general EclipseLink with Derby server is slightly more efficient than OpenJPA with PostgreSQL server in performing JPA database operations.
A huge 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 Derby database server (8.4) reveals that in that case, EclipseLink with Derby server is 11.7 times faster than OpenJPA with PostgreSQL server.
On the other hand, EclipseLink with Derby server is slower, for instance, when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (1.4) to the normalized speed of OpenJPA with PostgreSQL database server (4.6) reveals that in that case, EclipseLink with Derby server is 3.3 times slower than OpenJPA with PostgreSQL server.
Other Head to Head DBMS/JPA Comparisons
OpenJPA with PostgreSQL server against:
- Oracle Database 11g
- IBM DB2 10
- Microsoft SQL Server 2008
- DataNucleus with Derby embedded
- DataNucleus with H2 embedded
- DataNucleus with HSQLDB embedded
- DataNucleus with DB4O embedded
- DataNucleus with Derby server
- DataNucleus with H2 server
- DataNucleus with MySQL server
- DataNucleus with PostgreSQL server
- EclipseLink with Derby embedded
- EclipseLink with H2 embedded
- EclipseLink with HSQLDB embedded
- EclipseLink with SQLite embedded
- EclipseLink with Derby server
- EclipseLink with H2 server
- EclipseLink with MySQL server
- EclipseLink with PostgreSQL server
- Hibernate with Derby embedded
- Hibernate with H2 embedded
- Hibernate with HSQLDB embedded
- Hibernate with SQLite embedded
- Hibernate with Derby server
- Hibernate with H2 server
- Hibernate with MySQL server
- Hibernate with PostgreSQL server
- OpenJPA with Derby embedded
- OpenJPA with H2 embedded
- OpenJPA with HSQLDB embedded
- OpenJPA with Derby server
- OpenJPA with H2 server
- OpenJPA with MySQL server
- ObjectDB embedded
- ObjectDB server
EclipseLink with Derby server against:
- Oracle Database 11g
- IBM DB2 10
- Microsoft SQL Server 2008
- DataNucleus with Derby embedded
- DataNucleus with H2 embedded
- DataNucleus with HSQLDB embedded
- DataNucleus with DB4O embedded
- DataNucleus with Derby server
- DataNucleus with H2 server
- DataNucleus with MySQL server
- DataNucleus with PostgreSQL server
- EclipseLink with Derby embedded
- EclipseLink with H2 embedded
- EclipseLink with HSQLDB embedded
- EclipseLink with SQLite embedded
- EclipseLink with H2 server
- EclipseLink with MySQL server
- EclipseLink with PostgreSQL server
- Hibernate with Derby embedded
- Hibernate with H2 embedded
- Hibernate with HSQLDB embedded
- Hibernate with SQLite embedded
- Hibernate with Derby server
- Hibernate with H2 server
- Hibernate with MySQL server
- Hibernate with PostgreSQL server
- OpenJPA with Derby embedded
- OpenJPA with H2 embedded
- OpenJPA with HSQLDB embedded
- OpenJPA with Derby server
- OpenJPA with H2 server
- OpenJPA with MySQL server
- OpenJPA with PostgreSQL server
- ObjectDB embedded
- ObjectDB server
