Comparison of EclipseLink with Derby embedded vs Hibernate with SQLite 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 Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded |
Basic Person Test | 5.5 | 0.083 | 3.7 | 1.0 | 4.6 | 0.55 |
Element Collection Test | 3.0 | 0.067 | 1.7 | 0.69 | 2.4 | 0.38 |
Inheritance Test | 5.3 | 0.080 | 3.5 | 0.99 | 4.4 | 0.54 |
Indexing Test | 6.9 | 0.098 | 4.6 | 1.0 | 5.8 | 0.55 |
Graph (Binary Tree) Test | 2.0 | 0.27 | 1.9 | 0.96 | 1.9 | 0.61 |
Multithreading Test | 9.3 | failed | 4.1 | failed | 6.7 | failed |
All Tests | 5.3 | 0.12 | 3.2 | 0.93 | 4.3 | 0.53 |
Hibernate with SQLite embedded has failed in 2 tests (see exceptions).
The results above show that in general EclipseLink with Derby embedded is much more efficient than Hibernate with SQLite embedded in persisting JPA entity objects to the database. Comparing the normalized speed of Hibernate with SQLite embedded database (0.53) to the normalized speed of EclipseLink with Derby embedded database (4.3) reveals that in these tests, EclipseLink with Derby embedded is 8.1 times faster than Hibernate with SQLite embedded.
A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.098) to the normalized speed of EclipseLink with Derby embedded database (6.9) reveals that in that case, EclipseLink with Derby embedded is 70.4 times faster than Hibernate with SQLite embedded.
Speed comparison of JPA database retrieval operations (normalized score, higher is better)
Retrieval Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded |
Basic Person Test | 16.4 | 1.8 | 58.7 | 1.3 | 37.5 | 1.5 |
Element Collection Test | 7.5 | 0.0008 | 13.3 | failed | 10.4 | 0.0008 |
Inheritance Test | 17.1 | 2.4 | 58.9 | 1.4 | 38.0 | 1.9 |
Indexing Test | 14.2 | 1.9 | 67.4 | 2.3 | 40.8 | 2.1 |
Graph (Binary Tree) Test | 2.8 | 0.56 | 5.7 | 0.88 | 4.2 | 0.72 |
Multithreading Test | 28.0 | failed | 48.7 | failed | 38.4 | failed |
All Tests | 14.3 | 1.3 | 42.1 | 1.5 | 28.2 | 1.4 |
Hibernate with SQLite embedded has failed in 3 tests (see exceptions).
The results above show that in general EclipseLink with Derby embedded is much more efficient than Hibernate with SQLite embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of Hibernate with SQLite embedded database (1.4) to the normalized speed of EclipseLink with Derby embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 20.1 times faster than Hibernate with SQLite embedded.
A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0008) to the normalized speed of EclipseLink with Derby embedded database (7.5) reveals that in that case, EclipseLink with Derby embedded is 9,375 times faster than Hibernate with SQLite embedded.
Speed comparison of JPA database query operations (normalized score, higher is better)
Retrieval Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded |
Basic Person Test | 53.4 | 1.1 | 13.8 | 0.22 | 33.6 | 0.65 |
Element Collection Test | 37.9 | 0.39 | 4.4 | failed | 21.2 | 0.39 |
Inheritance Test | 37.4 | 0.53 | 15.0 | 0.28 | 26.2 | 0.40 |
Indexing Test | 7.6 | 0.0011 | 49.3 | 0.43 | 28.4 | 0.21 |
Multithreading Test | 41.2 | failed | 6.1 | failed | 23.6 | failed |
All Tests | 35.5 | 0.50 | 17.7 | 0.31 | 26.6 | 0.42 |
Hibernate with SQLite embedded has failed in 3 tests (see exceptions).
The results above show that in general EclipseLink with Derby embedded is much more efficient than Hibernate with SQLite embedded in executing the tested JPA queries. Comparing the normalized speed of Hibernate with SQLite embedded database (0.42) to the normalized speed of EclipseLink with Derby embedded database (26.6) reveals that in these tests, EclipseLink with Derby embedded is 63.3 times faster than Hibernate with SQLite embedded.
A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0011) to the normalized speed of EclipseLink with Derby embedded database (7.6) reveals that in that case, EclipseLink with Derby embedded is 6,909 times faster than Hibernate with SQLite embedded.
Speed comparison of JPA database update operations (normalized score, higher is better)
Transaction Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded |
Basic Person Test | 6.4 | 0.076 | 6.7 | 0.65 | 6.5 | 0.37 |
Element Collection Test | 5.4 | 0.0022 | 6.2 | failed | 5.8 | 0.0022 |
Inheritance Test | 6.5 | 0.079 | 9.2 | 0.97 | 7.8 | 0.53 |
Indexing Test | 7.3 | 0.057 | 11.1 | 0.54 | 9.2 | 0.30 |
Graph (Binary Tree) Test | 2.8 | 0.26 | 1.7 | 0.42 | 2.2 | 0.34 |
Multithreading Test | 21.3 | failed | 5.0 | failed | 13.1 | failed |
All Tests | 8.3 | 0.094 | 6.6 | 0.65 | 7.5 | 0.34 |
Hibernate with SQLite embedded has failed in 3 tests (see exceptions).
The results above show that in general EclipseLink with Derby embedded is much more efficient than Hibernate with SQLite embedded in updating JPA entity objects in the database. Comparing the normalized speed of Hibernate with SQLite embedded database (0.34) to the normalized speed of EclipseLink with Derby embedded database (7.5) reveals that in these tests, EclipseLink with Derby embedded is 22.1 times faster than Hibernate with SQLite embedded.
A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0022) to the normalized speed of EclipseLink with Derby embedded database (5.4) reveals that in that case, EclipseLink with Derby embedded is 2,455 times faster than Hibernate with SQLite embedded.
Speed comparison of JPA database removal operations (normalized score, higher is better)
Transaction Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded |
Basic Person Test | 4.6 | 0.061 | 4.7 | 0.91 | 4.6 | 0.49 |
Element Collection Test | 2.5 | 0.0007 | 1.4 | failed | 1.9 | 0.0007 |
Inheritance Test | 3.9 | 0.058 | 4.5 | 0.90 | 4.2 | 0.48 |
Indexing Test | 6.2 | 0.079 | 3.8 | 0.54 | 5.0 | 0.31 |
Graph (Binary Tree) Test | 1.1 | 0.24 | 1.0 | 0.80 | 1.1 | 0.52 |
Multithreading Test | 6.2 | failed | 5.8 | failed | 6.0 | failed |
All Tests | 4.1 | 0.088 | 3.5 | 0.79 | 3.8 | 0.40 |
Hibernate with SQLite embedded has failed in 3 tests (see exceptions).
The results above show that in general EclipseLink with Derby embedded is much more efficient than Hibernate with SQLite embedded in deleting JPA entity objects from the database. Comparing the normalized speed of Hibernate with SQLite embedded database (0.40) to the normalized speed of EclipseLink with Derby embedded database (3.8) reveals that in these tests, EclipseLink with Derby embedded is 9.5 times faster than Hibernate with SQLite embedded.
A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0007) to the normalized speed of EclipseLink with Derby embedded database (2.5) reveals that in that case, EclipseLink with Derby embedded is 3,571 times faster than Hibernate with SQLite embedded.
Comparison of database storage efficiency (normalized score, higher is better)
Transaction Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded |
Basic Person Test | 51.1 | 90.2 | 51.0 | 90.2 | 51.1 | 90.2 |
Element Collection Test | 38.5 | 82.0 | 39.4 | 82.0 | 38.9 | 82.0 |
Inheritance Test | 48.0 | 80.5 | 47.9 | 80.5 | 48.0 | 80.5 |
Indexing Test | 51.6 | 93.4 | 52.3 | 94.8 | 52.0 | 94.1 |
Graph (Binary Tree) Test | 13.4 | 67.9 | 11.7 | 50.9 | 12.6 | 59.4 |
Multithreading Test | 52.6 | failed | 8.4 | failed | 30.5 | failed |
All Tests | 42.5 | 82.8 | 35.1 | 79.7 | 38.8 | 81.2 |
Hibernate with SQLite embedded has failed in 2 tests (see exceptions).
The results above show that in general Hibernate with SQLite embedded is more efficient than EclipseLink with Derby embedded in using disk space. Comparing the normalized score of EclipseLink with Derby embedded database (38.8) to the normalized score of Hibernate with SQLite embedded database (81.2) reveals that in these tests, Hibernate with SQLite embedded is 2.1 times more efficient than EclipseLink with Derby embedded.
A large gap has been detected when using graphs of objects with small transaction size. Comparing the normalized score of EclipseLink with Derby embedded database (13.4) to the normalized score of Hibernate with SQLite embedded database (67.9) reveals that in that case, Hibernate with SQLite embedded is 5.1 times more efficient than EclipseLink with Derby embedded.
Comparison of JPA/Database speed - the averages (normalized score, higher is better)
Transaction/Retrieval Size | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded | EclipseLink Derby embedded | Hibernate SQLite embedded |
Basic Person Test | 17.3 | 0.63 | 17.5 | 0.81 | 17.4 | 0.72 |
Element Collection Test | 11.3 | 0.092 | 5.4 | 0.69 | 8.3 | 0.19 |
Inheritance Test | 14.0 | 0.63 | 18.2 | 0.91 | 16.1 | 0.77 |
Indexing Test | 8.4 | 0.42 | 27.2 | 0.96 | 17.8 | 0.69 |
Graph (Binary Tree) Test | 2.2 | 0.33 | 2.6 | 0.77 | 2.4 | 0.55 |
Multithreading Test | 21.2 | failed | 13.9 | failed | 17.6 | failed |
All Tests | 12.7 | 0.42 | 14.5 | 0.86 | 13.6 | 0.62 |
The results above show that in general EclipseLink with Derby embedded is much more efficient than Hibernate with SQLite embedded in performing JPA database operations. Comparing the normalized speed of Hibernate with SQLite embedded database (0.62) to the normalized speed of EclipseLink with Derby embedded database (13.6) reveals that in these tests, EclipseLink with Derby embedded is 21.9 times faster than Hibernate with SQLite embedded.
A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.092) to the normalized speed of EclipseLink with Derby embedded database (11.3) reveals that in that case, EclipseLink with Derby embedded is 123 times faster than Hibernate with SQLite embedded.
Other Head to Head DBMS/JPA Comparisons
EclipseLink with Derby 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 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
Hibernate with SQLite 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 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 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