Comparison of EclipseLink with HSQLDB embedded vs DataNucleus with Derby embedded
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 | |||
|---|---|---|---|---|---|---|
| EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | |
| Basic Person Test | 27.1 | 4.6 | 17.2 | 2.8 | 22.2 | 3.7 |
| Element Collection Test | 17.2 | 2.4 | 8.2 | 1.6 | 12.7 | 2.0 |
| Inheritance Test | 26.7 | 4.6 | 11.9 | 2.7 | 19.3 | 3.7 |
| Indexing Test | 30.6 | 7.6 | 18.6 | 4.8 | 24.6 | 6.2 |
| Graph (Binary Tree) Test | 20.0 | 1.6 | 15.9 | 1.4 | 18.0 | 1.5 |
| Multithreading Test | 32.5 | 8.6 | 11.4 | 3.3 | 22.0 | 5.9 |
| All Tests | 25.7 | 4.9 | 13.9 | 2.8 | 19.8 | 3.8 |
The results above show that in general EclipseLink with HSQLDB embedded is much more efficient than DataNucleus with Derby embedded in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with Derby embedded database (3.8) to the normalized speed of EclipseLink with HSQLDB embedded database (19.8) reveals that in these tests, EclipseLink with HSQLDB embedded is 5.2 times faster than DataNucleus with Derby embedded.
A huge performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (1.6) to the normalized speed of EclipseLink with HSQLDB embedded database (20.0) reveals that in that case, EclipseLink with HSQLDB embedded is 12.5 times faster than DataNucleus with Derby embedded.
Speed comparison of JPA database retrieval operations (normalized score, higher is better)
| Retrieval Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | |
| Basic Person Test | 24.4 | 6.8 | 36.0 | 14.9 | 30.2 | 10.9 |
| Element Collection Test | 14.9 | 5.4 | 19.1 | 7.6 | 17.0 | 6.5 |
| Inheritance Test | 22.8 | 8.8 | 40.0 | 14.8 | 31.4 | 11.8 |
| Indexing Test | 20.7 | 9.2 | 38.7 | 14.1 | 29.7 | 11.6 |
| Graph (Binary Tree) Test | 8.7 | 9.9 | 14.2 | 15.8 | 11.4 | 12.9 |
| Multithreading Test | 24.2 | 11.9 | 28.0 | 11.5 | 26.1 | 11.7 |
| All Tests | 19.3 | 8.7 | 29.3 | 13.1 | 24.3 | 10.9 |
The results above show that in general EclipseLink with HSQLDB embedded is more efficient than DataNucleus with Derby embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby embedded database (10.9) to the normalized speed of EclipseLink with HSQLDB embedded database (24.3) reveals that in these tests, EclipseLink with HSQLDB embedded is 2.2 times faster than DataNucleus with Derby embedded.
A large performance gap has been detected when using simple basic entities with small retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (6.8) to the normalized speed of EclipseLink with HSQLDB embedded database (24.4) reveals that in that case, EclipseLink with HSQLDB embedded is 3.6 times faster than DataNucleus with Derby embedded.
Speed comparison of JPA database query operations (normalized score, higher is better)
| Retrieval Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | |
| Basic Person Test | 2.9 | 39.1 | 0.88 | 7.5 | 1.9 | 23.3 |
| Element Collection Test | 3.2 | 46.0 | 1.4 | 6.7 | 2.3 | 26.3 |
| Inheritance Test | 2.6 | 7.7 | 1.1 | 3.8 | 1.9 | 5.7 |
| Indexing Test | 21.5 | 0.053 | 33.3 | 8.0 | 27.4 | 4.0 |
| Multithreading Test | 1.1 | failed | 0.52 | failed | 0.82 | failed |
| All Tests | 6.3 | 23.2 | 7.4 | 6.5 | 6.9 | 14.8 |
DataNucleus with Derby embedded has failed in 2 tests (see exceptions).
The results above show that in general DataNucleus with Derby embedded is more efficient than EclipseLink with HSQLDB embedded in executing the tested JPA queries. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (6.9) to the normalized speed of DataNucleus with Derby embedded database (14.8) reveals that in these tests, DataNucleus with Derby embedded is 2.1 times faster than EclipseLink with HSQLDB embedded.
A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (3.2) to the normalized speed of DataNucleus with Derby embedded database (46.0) reveals that in that case, DataNucleus with Derby embedded is 14.4 times faster than EclipseLink with HSQLDB embedded.
On the other hand, DataNucleus with Derby embedded is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (0.053) to the normalized speed of EclipseLink with HSQLDB embedded database (21.5) reveals that in that case, DataNucleus with Derby embedded is 406 times slower than EclipseLink with HSQLDB embedded.
Speed comparison of JPA database update operations (normalized score, higher is better)
| Transaction Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | |
| Basic Person Test | 17.9 | 4.0 | 7.0 | 3.8 | 12.5 | 3.9 |
| Element Collection Test | 14.6 | 3.7 | 8.3 | 4.5 | 11.4 | 4.1 |
| Inheritance Test | 16.2 | 4.4 | 9.7 | 4.8 | 13.0 | 4.6 |
| Indexing Test | 12.0 | 5.2 | 6.8 | 4.2 | 9.4 | 4.7 |
| Graph (Binary Tree) Test | 4.7 | 2.7 | 3.4 | 1.5 | 4.0 | 2.1 |
| Multithreading Test | 24.4 | failed | 4.4 | failed | 14.4 | failed |
| All Tests | 15.0 | 4.0 | 6.6 | 3.7 | 10.8 | 3.9 |
DataNucleus with Derby embedded has failed in 2 tests (see exceptions).
The results above show that in general EclipseLink with HSQLDB embedded is more efficient than DataNucleus with Derby embedded in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with Derby embedded database (3.9) to the normalized speed of EclipseLink with HSQLDB embedded database (10.8) reveals that in these tests, EclipseLink with HSQLDB embedded is 2.8 times faster than DataNucleus with Derby embedded.
A large performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (4.0) to the normalized speed of EclipseLink with HSQLDB embedded database (17.9) reveals that in that case, EclipseLink with HSQLDB embedded is 4.5 times faster than DataNucleus with Derby embedded.
Speed comparison of JPA database removal operations (normalized score, higher is better)
| Transaction Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | |
| Basic Person Test | 32.3 | 3.5 | 20.3 | 1.3 | 26.3 | 2.4 |
| Element Collection Test | 14.3 | 1.9 | 6.0 | 1.6 | 10.2 | 1.7 |
| Inheritance Test | 29.2 | 2.4 | 23.9 | 1.3 | 26.6 | 1.9 |
| Indexing Test | 55.3 | 6.6 | 27.1 | 1.9 | 41.2 | 4.3 |
| Graph (Binary Tree) Test | 6.8 | 0.81 | 14.1 | 0.93 | 10.4 | 0.87 |
| Multithreading Test | 52.9 | failed | 28.4 | failed | 40.6 | failed |
| All Tests | 31.8 | 3.0 | 20.0 | 1.4 | 25.9 | 2.2 |
DataNucleus with Derby embedded has failed in 2 tests (see exceptions).
The results above show that in general EclipseLink with HSQLDB embedded is much more efficient than DataNucleus with Derby embedded in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby embedded database (2.2) to the normalized speed of EclipseLink with HSQLDB embedded database (25.9) reveals that in these tests, EclipseLink with HSQLDB embedded is 11.8 times faster than DataNucleus with Derby embedded.
A huge performance gap has been detected when using class inheritance in the object model with large transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (1.3) to the normalized speed of EclipseLink with HSQLDB embedded database (23.9) reveals that in that case, EclipseLink with HSQLDB embedded is 18.4 times faster than DataNucleus with Derby embedded.
Comparison of database storage efficiency (normalized score, higher is better)
| Transaction Size => | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | |
| Basic Person Test | 41.4 | 53.3 | 41.4 | 53.3 | 41.4 | 53.3 |
| Element Collection Test | 46.9 | 42.6 | 46.9 | 42.6 | 46.9 | 42.6 |
| Inheritance Test | 41.4 | 48.1 | 41.4 | 48.1 | 41.4 | 48.1 |
| Indexing Test | 48.4 | 62.3 | 49.2 | 63.3 | 48.8 | 62.8 |
| Graph (Binary Tree) Test | 28.5 | 13.6 | 21.4 | 10.2 | 25.0 | 11.9 |
| Multithreading Test | 51.9 | 52.0 | 10.3 | 8.0 | 31.1 | 30.0 |
| All Tests | 43.1 | 45.3 | 35.1 | 37.6 | 39.1 | 41.5 |
The results above show that in general DataNucleus with Derby embedded is slightly more efficient than EclipseLink with HSQLDB embedded in using disk space.
On the other hand, DataNucleus with Derby embedded is slower, for instance, when using graphs of objects with large transaction size. Comparing the normalized score of DataNucleus with Derby embedded database (10.2) to the normalized score of EclipseLink with HSQLDB embedded database (21.4) reveals that in that case, DataNucleus with Derby embedded is 2.1 times less efficient than EclipseLink with HSQLDB embedded.
Comparison of JPA/Database speed - the averages (normalized score, higher is better)
| Transaction/Retrieval Size | Few Entities | Many Entities | Average Score | |||
|---|---|---|---|---|---|---|
| EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | EclipseLink HSQLDB embedded | DataNucleus Derby embedded | |
| Basic Person Test | 20.9 | 11.6 | 16.3 | 6.1 | 18.6 | 8.8 |
| Element Collection Test | 12.8 | 11.9 | 8.6 | 4.4 | 10.7 | 8.1 |
| Inheritance Test | 19.5 | 5.6 | 17.3 | 5.5 | 18.4 | 5.5 |
| Indexing Test | 28.0 | 5.7 | 24.9 | 6.6 | 26.5 | 6.2 |
| Graph (Binary Tree) Test | 10.0 | 3.7 | 11.9 | 4.9 | 11.0 | 4.3 |
| Multithreading Test | 27.0 | 10.3 | 14.6 | 7.4 | 20.8 | 8.8 |
| All Tests | 20.1 | 8.0 | 15.7 | 5.7 | 17.9 | 6.9 |
The results above show that in general EclipseLink with HSQLDB embedded is more efficient than DataNucleus with Derby embedded in performing JPA database operations. Comparing the normalized speed of DataNucleus with Derby embedded database (6.9) to the normalized speed of EclipseLink with HSQLDB embedded database (17.9) reveals that in these tests, EclipseLink with HSQLDB embedded is 2.6 times faster than DataNucleus with Derby embedded.
A large performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (5.7) to the normalized speed of EclipseLink with HSQLDB embedded database (28.0) reveals that in that case, EclipseLink with HSQLDB embedded is 4.9 times faster than DataNucleus with Derby embedded.
Other Head to Head DBMS/JPA Comparisons
EclipseLink with HSQLDB 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 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 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
DataNucleus with Derby embedded against:
- Oracle Database 11g
- IBM DB2 10
- Microsoft SQL Server 2008
- 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
- OpenJPA with PostgreSQL server
- ObjectDB embedded
- ObjectDB server
