Comparison of DataNucleus with Derby server 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 Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | |
| Basic Person Test | 2.8 | 7.3 | 2.3 | 4.2 | 2.6 | 5.8 |
| Element Collection Test | 0.71 | 3.1 | 0.35 | 1.9 | 0.53 | 2.5 |
| Inheritance Test | 2.7 | 6.9 | 2.0 | 5.0 | 2.3 | 5.9 |
| Indexing Test | 4.5 | 10.0 | 4.0 | 6.8 | 4.3 | 8.4 |
| Graph (Binary Tree) Test | 0.62 | 3.5 | 0.53 | 3.3 | 0.57 | 3.4 |
| Multithreading Test | 4.9 | 31.8 | 3.4 | 14.5 | 4.1 | 23.1 |
| All Tests | 2.7 | 10.4 | 2.1 | 6.0 | 2.4 | 8.2 |
The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with Derby server in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with Derby database server (2.4) to the normalized speed of EclipseLink with PostgreSQL database server (8.2) reveals that in these tests, EclipseLink with PostgreSQL server is 3.4 times faster than DataNucleus with Derby server.
A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (4.9) to the normalized speed of EclipseLink with PostgreSQL database server (31.8) reveals that in that case, EclipseLink with PostgreSQL server is 6.5 times faster than DataNucleus with Derby server.
Speed comparison of JPA database retrieval operations (normalized score, higher is better)
| Retrieval Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | |
| Basic Person Test | 0.56 | 6.8 | 6.3 | 17.2 | 3.4 | 12.0 |
| Element Collection Test | 0.36 | 0.026 | 0.93 | 0.020 | 0.64 | 0.023 |
| Inheritance Test | 0.45 | 6.0 | 6.8 | 19.7 | 3.6 | 12.9 |
| Indexing Test | 0.50 | 5.6 | 7.1 | 19.5 | 3.8 | 12.6 |
| Graph (Binary Tree) Test | 0.22 | 0.47 | 6.6 | 0.61 | 3.4 | 0.54 |
| Multithreading Test | 1.2 | 13.5 | 10.0 | 27.8 | 5.6 | 20.6 |
| All Tests | 0.55 | 5.4 | 6.3 | 14.1 | 3.4 | 9.8 |
The results above show that in general EclipseLink with PostgreSQL server is more efficient than DataNucleus with Derby server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby database server (3.4) to the normalized speed of EclipseLink with PostgreSQL database server (9.8) reveals that in these tests, EclipseLink with PostgreSQL server is 2.9 times faster than DataNucleus with Derby server.
A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.45) to the normalized speed of EclipseLink with PostgreSQL database server (6.0) reveals that in that case, EclipseLink with PostgreSQL server is 13.3 times faster than DataNucleus with Derby 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 DataNucleus with Derby database server (0.93) reveals that in that case, EclipseLink with PostgreSQL server is 46.5 times slower than DataNucleus with Derby server.
Speed comparison of JPA database query operations (normalized score, higher is better)
| Retrieval Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | |
| Basic Person Test | 37.7 | 55.5 | 3.6 | 7.8 | 20.7 | 31.6 |
| Element Collection Test | 25.9 | 15.4 | 1.4 | 0.028 | 13.6 | 7.7 |
| Inheritance Test | 6.5 | 54.9 | 1.8 | 11.5 | 4.2 | 33.2 |
| Indexing Test | 0.030 | 0.077 | 4.9 | 10.0 | 2.5 | 5.1 |
| Multithreading Test | failed | 55.3 | failed | 12.0 | failed | 33.7 |
| All Tests | 17.5 | 36.2 | 2.9 | 8.3 | 10.2 | 22.3 |
DataNucleus with Derby server has failed in 2 tests (see exceptions).
The results above show that in general EclipseLink with PostgreSQL server is more efficient than DataNucleus with Derby server in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with Derby database server (10.2) to the normalized speed of EclipseLink with PostgreSQL database server (22.3) reveals that in these tests, EclipseLink with PostgreSQL server is 2.2 times faster than DataNucleus with Derby server.
A large performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (6.5) to the normalized speed of EclipseLink with PostgreSQL database server (54.9) reveals that in that case, EclipseLink with PostgreSQL server is 8.4 times faster than DataNucleus with Derby 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.028) to the normalized speed of DataNucleus with Derby database server (1.4) reveals that in that case, EclipseLink with PostgreSQL server is 50.0 times slower than DataNucleus with Derby server.
Speed comparison of JPA database update operations (normalized score, higher is better)
| Transaction Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | |
| Basic Person Test | 1.1 | 6.2 | 0.85 | 4.1 | 0.99 | 5.1 |
| Element Collection Test | 0.81 | 0.080 | 0.62 | 0.028 | 0.71 | 0.054 |
| Inheritance Test | 1.2 | 6.4 | 1.3 | 6.1 | 1.2 | 6.2 |
| Indexing Test | 1.2 | 6.5 | 1.5 | 7.0 | 1.3 | 6.8 |
| Graph (Binary Tree) Test | 0.29 | 0.90 | 0.41 | 0.50 | 0.35 | 0.70 |
| Multithreading Test | failed | 36.0 | failed | 9.1 | failed | 22.5 |
| All Tests | 0.93 | 9.3 | 0.92 | 4.5 | 0.92 | 6.9 |
DataNucleus with Derby server has failed in 2 tests (see exceptions).
The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with Derby server in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with Derby database server (0.92) to the normalized speed of EclipseLink with PostgreSQL database server (6.9) reveals that in these tests, EclipseLink with PostgreSQL server is 7.5 times faster than DataNucleus with Derby server.
A large performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (1.1) to the normalized speed of EclipseLink with PostgreSQL database server (6.2) reveals that in that case, EclipseLink with PostgreSQL server is 5.6 times faster than DataNucleus with Derby 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 DataNucleus with Derby database server (0.62) reveals that in that case, EclipseLink with PostgreSQL server is 22.1 times slower than DataNucleus with Derby server.
Speed comparison of JPA database removal operations (normalized score, higher is better)
| Transaction Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | |
| Basic Person Test | 1.3 | 5.7 | 1.3 | 5.7 | 1.3 | 5.7 |
| Element Collection Test | 0.61 | 0.025 | 0.33 | stopped | 0.47 | 0.012 |
| Inheritance Test | 1.0 | 5.5 | 1.3 | 5.4 | 1.2 | 5.4 |
| Indexing Test | 2.3 | 10.4 | 1.9 | 10.0 | 2.1 | 10.2 |
| Graph (Binary Tree) Test | 0.26 | 0.016 | 0.46 | 0.013 | 0.36 | 0.015 |
| Multithreading Test | failed | 26.3 | failed | 16.8 | failed | 21.6 |
| All Tests | 1.1 | 8.0 | 1.1 | 6.3 | 1.1 | 7.2 |
DataNucleus with Derby server has failed in 2 tests (see exceptions).
The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with Derby server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby database server (1.1) to the normalized speed of EclipseLink with PostgreSQL database server (7.2) reveals that in these tests, EclipseLink with PostgreSQL server is 6.5 times faster than DataNucleus with Derby server.
A large performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (1.0) to the normalized speed of EclipseLink with PostgreSQL database server (5.5) reveals that in that case, EclipseLink with PostgreSQL server is 5.5 times faster than DataNucleus with Derby server.
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 DataNucleus with Derby database server (0.46) reveals that in that case, EclipseLink with PostgreSQL server is 35.4 times slower than DataNucleus with Derby server.
Comparison of JPA/Database speed - the averages (normalized score, higher is better)
| Transaction/Retrieval Size | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | DataNucleus Derby server | EclipseLink PostgreSQL server | |
| Basic Person Test | 8.7 | 16.3 | 2.9 | 7.8 | 5.8 | 12.1 |
| Element Collection Test | 5.7 | 3.7 | 0.72 | 0.40 | 3.2 | 2.1 |
| Inheritance Test | 2.4 | 15.9 | 2.6 | 9.5 | 2.5 | 12.7 |
| Indexing Test | 1.7 | 6.5 | 3.9 | 10.7 | 2.8 | 8.6 |
| Graph (Binary Tree) Test | 0.35 | 1.2 | 2.0 | 1.1 | 1.2 | 1.2 |
| Multithreading Test | 3.0 | 32.6 | 6.7 | 16.0 | 4.9 | 24.3 |
| All Tests | 3.8 | 13.1 | 2.8 | 7.8 | 3.3 | 10.5 |
The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with Derby server in performing JPA database operations. Comparing the normalized speed of DataNucleus with Derby database server (3.3) to the normalized speed of EclipseLink with PostgreSQL database server (10.5) reveals that in these tests, EclipseLink with PostgreSQL server is 3.2 times faster than DataNucleus with Derby server.
A huge performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (3.0) to the normalized speed of EclipseLink with PostgreSQL database server (32.6) reveals that in that case, EclipseLink with PostgreSQL server is 10.9 times faster than DataNucleus with Derby server.
Other Head to Head DBMS/JPA Comparisons
DataNucleus 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 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
- OpenJPA with PostgreSQL server
- ObjectDB embedded
- ObjectDB server
EclipseLink 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
- 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
