Comparison of DataNucleus with DB4O embedded 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 | |||
|---|---|---|---|---|---|---|
| DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | |
| Basic Person Test | 0.059 | 3.8 | 1.3 | 3.1 | 0.69 | 3.4 |
| Element Collection Test | 0.045 | 2.2 | 1.0 | 1.5 | 0.52 | 1.8 |
| Inheritance Test | 0.051 | 3.9 | 0.85 | 2.9 | 0.45 | 3.4 |
| Indexing Test | 0.080 | 5.2 | 2.3 | 4.3 | 1.2 | 4.7 |
| Graph (Binary Tree) Test | failed | 1.9 | failed | 1.7 | failed | 1.8 |
| Multithreading Test | failed | 6.1 | failed | 3.9 | failed | 5.0 |
| All Tests | 0.059 | 3.8 | 1.4 | 2.9 | 0.71 | 3.4 |
DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).
The results above show that in general EclipseLink with Derby server is much more efficient than DataNucleus with DB4O embedded in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.71) to the normalized speed of EclipseLink with Derby database server (3.4) reveals that in these tests, EclipseLink with Derby server is 4.8 times faster than DataNucleus with DB4O embedded.
A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.051) to the normalized speed of EclipseLink with Derby database server (3.9) reveals that in that case, EclipseLink with Derby server is 76.5 times faster than DataNucleus with DB4O embedded.
Speed comparison of JPA database retrieval operations (normalized score, higher is better)
| Retrieval Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | |
| Basic Person Test | 0.0047 | 6.4 | 1.8 | 11.3 | 0.90 | 8.8 |
| Element Collection Test | 0.0038 | 1.8 | 1.5 | 2.4 | 0.77 | 2.1 |
| Inheritance Test | 0.0035 | 3.7 | 2.2 | 12.9 | 1.1 | 8.3 |
| Indexing Test | 0.0043 | 3.6 | 1.8 | 12.8 | 0.89 | 8.2 |
| Graph (Binary Tree) Test | failed | 0.61 | failed | 0.73 | failed | 0.67 |
| Multithreading Test | failed | 8.5 | failed | 19.8 | failed | 14.1 |
| All Tests | 0.0041 | 4.1 | 1.8 | 10.0 | 0.91 | 7.0 |
DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).
The results above show that in general EclipseLink with Derby server is much more efficient than DataNucleus with DB4O embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.91) to the normalized speed of EclipseLink with Derby database server (7.0) reveals that in these tests, EclipseLink with Derby server is 7.7 times faster than DataNucleus with DB4O embedded.
A huge performance gap has been detected when using simple basic entities with small retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0047) to the normalized speed of EclipseLink with Derby database server (6.4) reveals that in that case, EclipseLink with Derby server is 1,362 times faster than DataNucleus with DB4O embedded.
Speed comparison of JPA database query operations (normalized score, higher is better)
| Retrieval Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | 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 |
DataNucleus with DB4O embedded 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 | |||
|---|---|---|---|---|---|---|
| DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | |
| Basic Person Test | 0.012 | 3.9 | 0.76 | 4.4 | 0.39 | 4.1 |
| Element Collection Test | 0.012 | 1.7 | 1.1 | 1.6 | 0.53 | 1.6 |
| Inheritance Test | 0.011 | 4.6 | 0.81 | 6.1 | 0.41 | 5.3 |
| Indexing Test | 0.011 | 4.5 | 1.3 | 7.6 | 0.64 | 6.1 |
| Graph (Binary Tree) Test | failed | 0.70 | failed | 0.42 | failed | 0.56 |
| Multithreading Test | failed | 7.3 | failed | 4.8 | failed | 6.0 |
| All Tests | 0.012 | 3.8 | 0.97 | 4.2 | 0.49 | 4.0 |
DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).
The results above show that in general EclipseLink with Derby server is much more efficient than DataNucleus with DB4O embedded in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.49) to the normalized speed of EclipseLink with Derby database server (4.0) reveals that in these tests, EclipseLink with Derby server is 8.2 times faster than DataNucleus with DB4O embedded.
A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.011) to the normalized speed of EclipseLink with Derby database server (4.6) reveals that in that case, EclipseLink with Derby server is 418 times faster than DataNucleus with DB4O embedded.
Speed comparison of JPA database removal operations (normalized score, higher is better)
| Transaction Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | |
| Basic Person Test | 0.011 | 2.8 | 1.5 | 3.9 | 0.74 | 3.3 |
| Element Collection Test | 0.010 | 1.2 | 1.6 | 0.55 | 0.80 | 0.87 |
| Inheritance Test | 0.0093 | 3.3 | 1.1 | 3.7 | 0.57 | 3.5 |
| Indexing Test | 0.017 | 4.9 | 2.1 | 3.5 | 1.1 | 4.2 |
| Graph (Binary Tree) Test | failed | 0.51 | failed | 0.50 | failed | 0.51 |
| Multithreading Test | failed | 4.8 | failed | 5.7 | failed | 5.3 |
| All Tests | 0.012 | 2.9 | 1.6 | 3.0 | 0.79 | 3.0 |
DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).
The results above show that in general EclipseLink with Derby server is much more efficient than DataNucleus with DB4O embedded in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.79) to the normalized speed of EclipseLink with Derby database server (3.0) reveals that in these tests, EclipseLink with Derby server is 3.8 times faster than DataNucleus with DB4O embedded.
A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0093) to the normalized speed of EclipseLink with Derby database server (3.3) reveals that in that case, EclipseLink with Derby server is 355 times faster than DataNucleus with DB4O embedded.
On the other hand, EclipseLink with Derby server is slower, for instance, 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 DataNucleus with DB4O embedded database (1.6) reveals that in that case, EclipseLink with Derby server is 2.9 times slower than DataNucleus with DB4O embedded.
Comparison of JPA/Database speed - the averages (normalized score, higher is better)
| Transaction/Retrieval Size | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | DataNucleus DB4O embedded | EclipseLink Derby server | |
| Basic Person Test | 0.022 | 12.5 | 1.3 | 5.6 | 0.68 | 9.1 |
| Element Collection Test | 0.018 | 8.4 | 1.3 | 1.4 | 0.66 | 4.9 |
| Inheritance Test | 0.019 | 7.7 | 1.2 | 6.3 | 0.63 | 7.0 |
| Indexing Test | 0.028 | 4.1 | 1.9 | 8.1 | 0.94 | 6.1 |
| Graph (Binary Tree) Test | failed | 0.93 | failed | 0.83 | failed | 0.88 |
| Multithreading Test | failed | 12.2 | failed | 8.4 | failed | 10.3 |
| All Tests | 0.022 | 7.9 | 1.4 | 5.2 | 0.73 | 6.6 |
The results above show that in general EclipseLink with Derby server is much more efficient than DataNucleus with DB4O embedded in performing JPA database operations. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.73) to the normalized speed of EclipseLink with Derby database server (6.6) reveals that in these tests, EclipseLink with Derby server is 9.0 times faster than DataNucleus with DB4O embedded.
A huge performance gap has been detected when using simple basic entities with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.022) to the normalized speed of EclipseLink with Derby database server (12.5) reveals that in that case, EclipseLink with Derby server is 568 times faster than DataNucleus with DB4O embedded.
Other Head to Head DBMS/JPA Comparisons
DataNucleus with DB4O embedded 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 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
- OpenJPA with PostgreSQL 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
