Comparison of EclipseLink with PostgreSQL server vs ObjectDB 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 | |||
---|---|---|---|---|---|---|
  | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server |
Basic Person Test | 7.3 | 35.2 | 4.2 | 74.1 | 5.8 | 54.7 |
Element Collection Test | 3.1 | 38.2 | 1.9 | 57.8 | 2.5 | 48.0 |
Inheritance Test | 6.9 | 32.7 | 5.0 | 72.8 | 5.9 | 52.7 |
Indexing Test | 10.0 | 49.9 | 6.8 | 90.1 | 8.4 | 70.0 |
Graph (Binary Tree) Test | 3.5 | 100 | 3.3 | 89.2 | 3.4 | 94.6 |
Multithreading Test | 31.8 | 76.6 | 14.5 | 99.4 | 23.1 | 88.0 |
All Tests | 10.4 | 55.4 | 6.0 | 80.6 | 8.2 | 68.0 |
The results above show that in general ObjectDB server is much more efficient than EclipseLink with PostgreSQL server in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with PostgreSQL database server (8.2) to the normalized speed of ObjectDB database server (68.0) reveals that in these tests, ObjectDB server is 8.3 times faster than EclipseLink with PostgreSQL server.
A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (1.9) to the normalized speed of ObjectDB database server (57.8) reveals that in that case, ObjectDB server is 30.4 times faster than EclipseLink with PostgreSQL server.
Speed comparison of JPA database retrieval operations (normalized score, higher is better)
Retrieval Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server |
Basic Person Test | 6.8 | 15.7 | 17.2 | 45.4 | 12.0 | 30.5 |
Element Collection Test | 0.026 | 19.9 | 0.020 | 49.2 | 0.023 | 34.6 |
Inheritance Test | 6.0 | 13.2 | 19.7 | 49.4 | 12.9 | 31.3 |
Indexing Test | 5.6 | 14.0 | 19.5 | 59.5 | 12.6 | 36.8 |
Graph (Binary Tree) Test | 0.47 | 19.9 | 0.61 | 24.7 | 0.54 | 22.3 |
Multithreading Test | 13.5 | 19.7 | 27.8 | 60.2 | 20.6 | 40.0 |
All Tests | 5.4 | 17.1 | 14.1 | 48.1 | 9.8 | 32.6 |
The results above show that in general ObjectDB server is much more efficient than EclipseLink with PostgreSQL server in retrieving JPA entity objects from the database. Comparing the normalized speed of EclipseLink with PostgreSQL database server (9.8) to the normalized speed of ObjectDB database server (32.6) reveals that in these tests, ObjectDB server is 3.3 times faster than EclipseLink with PostgreSQL server.
A huge performance gap has been detected 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 ObjectDB database server (49.2) reveals that in that case, ObjectDB server is 2,460 times faster than EclipseLink with PostgreSQL server.
Speed comparison of JPA database query operations (normalized score, higher is better)
Retrieval Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server |
Basic Person Test | 55.5 | 38.8 | 7.8 | 25.9 | 31.6 | 32.4 |
Element Collection Test | 15.4 | 39.5 | 0.028 | 33.1 | 7.7 | 36.3 |
Inheritance Test | 54.9 | 34.8 | 11.5 | 34.0 | 33.2 | 34.4 |
Indexing Test | 0.077 | 14.5 | 10.0 | 53.3 | 5.1 | 33.9 |
Multithreading Test | 55.3 | 50.8 | 12.0 | 52.1 | 33.7 | 51.5 |
All Tests | 36.2 | 35.7 | 8.3 | 39.7 | 22.3 | 37.7 |
The results above show that in general ObjectDB server is more efficient than EclipseLink with PostgreSQL server in executing the tested JPA queries.
A huge performance gap has been detected 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 ObjectDB database server (33.1) reveals that in that case, ObjectDB server is 1,182 times faster than EclipseLink with PostgreSQL server.
Speed comparison of JPA database update operations (normalized score, higher is better)
Transaction Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server |
Basic Person Test | 6.2 | 18.3 | 4.1 | 40.9 | 5.1 | 29.6 |
Element Collection Test | 0.080 | 21.1 | 0.028 | 53.7 | 0.054 | 37.4 |
Inheritance Test | 6.4 | 19.9 | 6.1 | 51.9 | 6.2 | 35.9 |
Indexing Test | 6.5 | 17.9 | 7.0 | 52.1 | 6.8 | 35.0 |
Graph (Binary Tree) Test | 0.90 | 42.6 | 0.50 | 24.1 | 0.70 | 33.3 |
Multithreading Test | 36.0 | 68.6 | 9.1 | 68.7 | 22.5 | 68.6 |
All Tests | 9.3 | 31.4 | 4.5 | 48.6 | 6.9 | 40.0 |
The results above show that in general ObjectDB server is much more efficient than EclipseLink with PostgreSQL server in updating JPA entity objects in the database. Comparing the normalized speed of EclipseLink with PostgreSQL database server (6.9) to the normalized speed of ObjectDB database server (40.0) reveals that in these tests, ObjectDB server is 5.8 times faster than EclipseLink with PostgreSQL server.
A huge performance gap has been detected 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 ObjectDB database server (53.7) reveals that in that case, ObjectDB server is 1,918 times faster than EclipseLink with PostgreSQL server.
Speed comparison of JPA database removal operations (normalized score, higher is better)
Transaction Size => | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server |
Basic Person Test | 5.7 | 20.2 | 5.7 | 67.7 | 5.7 | 44.0 |
Element Collection Test | 0.025 | 22.9 | stopped | 57.6 | 0.012 | 40.2 |
Inheritance Test | 5.5 | 23.1 | 5.4 | 61.6 | 5.4 | 42.3 |
Indexing Test | 10.4 | 34.9 | 10.0 | 55.9 | 10.2 | 45.4 |
Graph (Binary Tree) Test | 0.016 | 19.3 | 0.013 | 27.9 | 0.015 | 23.6 |
Multithreading Test | 26.3 | 38.5 | 16.8 | 50.5 | 21.6 | 44.5 |
All Tests | 8.0 | 26.5 | 6.3 | 53.5 | 7.2 | 40.0 |
The results above show that in general ObjectDB server is much more efficient than EclipseLink with PostgreSQL server in deleting JPA entity objects from the database. Comparing the normalized speed of EclipseLink with PostgreSQL database server (7.2) to the normalized speed of ObjectDB database server (40.0) reveals that in these tests, ObjectDB server is 5.6 times faster than EclipseLink with PostgreSQL server.
A huge performance gap has been detected 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 ObjectDB database server (27.9) reveals that in that case, ObjectDB server is 2,146 times faster than EclipseLink with PostgreSQL server.
Comparison of JPA/Database speed - the averages (normalized score, higher is better)
Transaction/Retrieval Size | Few Entities | Many Entities | Average Score | |||
---|---|---|---|---|---|---|
  | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server | EclipseLink PostgreSQL server | ObjectDB server |
Basic Person Test | 16.3 | 25.6 | 7.8 | 50.8 | 12.1 | 38.2 |
Element Collection Test | 3.7 | 28.3 | 0.40 | 50.3 | 2.1 | 39.3 |
Inheritance Test | 15.9 | 24.7 | 9.5 | 53.9 | 12.7 | 39.3 |
Indexing Test | 6.5 | 26.2 | 10.7 | 62.2 | 8.6 | 44.2 |
Graph (Binary Tree) Test | 1.2 | 45.4 | 1.1 | 41.5 | 1.2 | 43.5 |
Multithreading Test | 32.6 | 50.8 | 16.0 | 66.2 | 24.3 | 58.5 |
All Tests | 13.1 | 33.1 | 7.8 | 54.6 | 10.5 | 43.9 |
The results above show that in general ObjectDB server is much more efficient than EclipseLink with PostgreSQL server in performing JPA database operations. Comparing the normalized speed of EclipseLink with PostgreSQL database server (10.5) to the normalized speed of ObjectDB database server (43.9) reveals that in these tests, ObjectDB server is 4.2 times faster than EclipseLink with PostgreSQL server.
A huge performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.40) to the normalized speed of ObjectDB database server (50.3) reveals that in that case, ObjectDB server is 126 times faster than EclipseLink with PostgreSQL server.
Other Head to Head DBMS/JPA Comparisons
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
ObjectDB 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
- OpenJPA with PostgreSQL server
- ObjectDB embedded