Comparison of EclipseLink with Derby server vs Hibernate 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
	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server
Basic Person Test	3.8	7.1	3.1	3.4	3.4	5.2
Element Collection Test	2.2	2.9	1.5	1.7	1.8	2.3
Inheritance Test	3.9	7.0	2.9	3.6	3.4	5.3
Indexing Test	5.2	9.3	4.3	6.1	4.7	7.7
Graph (Binary Tree) Test	1.9	3.0	1.7	2.9	1.8	2.9
Multithreading Test	6.1	31.7	3.9	13.9	5.0	22.8
All Tests	3.8	10.2	2.9	5.3	3.4	7.7

The results above show that in general Hibernate with PostgreSQL server is more efficient than EclipseLink with Derby server in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with Derby database server (3.4) to the normalized speed of Hibernate with PostgreSQL database server (7.7) reveals that in these tests, Hibernate with PostgreSQL server is 2.3 times faster than EclipseLink with Derby server.

A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby database server (6.1) to the normalized speed of Hibernate with PostgreSQL database server (31.7) reveals that in that case, Hibernate with PostgreSQL server is 5.2 times faster than EclipseLink with Derby server.

Speed comparison of JPA database retrieval operations (normalized score, higher is better)

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server
Basic Person Test	6.4	5.5	11.3	11.5	8.8	8.5
Element Collection Test	1.8	0.025	2.4	0.017	2.1	0.021
Inheritance Test	3.7	5.2	12.9	14.0	8.3	9.6
Indexing Test	3.6	4.6	12.8	13.3	8.2	8.9
Graph (Binary Tree) Test	0.61	0.61	0.73	0.78	0.67	0.70
Multithreading Test	8.5	11.3	19.8	17.0	14.1	14.2
All Tests	4.1	4.5	10.0	9.4	7.0	7.0

The results above show that in general EclipseLink with Derby server is equivalent to Hibernate with PostgreSQL server in retrieving JPA entity objects from the database.

A huge performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.017) to the normalized speed of EclipseLink with Derby database server (2.4) reveals that in that case, EclipseLink with Derby server is 141 times faster than Hibernate with PostgreSQL server.

Speed comparison of JPA database query operations (normalized score, higher is better)

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server
Basic Person Test	45.8	55.5	5.3	6.1	25.6	30.8
Element Collection Test	35.2	11.0	0.99	0.016	18.1	5.5
Inheritance Test	23.1	52.3	5.9	8.7	14.5	30.5
Indexing Test	2.5	0.050	12.2	8.8	7.4	4.4
Multithreading Test	34.3	55.2	7.7	9.2	21.0	32.2
All Tests	28.2	34.8	6.4	6.6	17.3	20.7

The results above show that in general Hibernate with PostgreSQL server is slightly more efficient than EclipseLink with Derby server in executing the tested JPA queries.

A large performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (23.1) to the normalized speed of Hibernate with PostgreSQL database server (52.3) reveals that in that case, Hibernate with PostgreSQL server is 2.3 times faster than EclipseLink with Derby server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.016) to the normalized speed of EclipseLink with Derby database server (0.99) reveals that in that case, Hibernate with PostgreSQL server is 61.9 times slower than EclipseLink with Derby server.

Speed comparison of JPA database update operations (normalized score, higher is better)

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server
Basic Person Test	3.9	5.3	4.4	2.7	4.1	4.0
Element Collection Test	1.7	0.067	1.6	0.026	1.6	0.046
Inheritance Test	4.6	5.4	6.1	3.8	5.3	4.6
Indexing Test	4.5	5.4	7.6	4.3	6.1	4.8
Graph (Binary Tree) Test	0.70	1.1	0.42	0.58	0.56	0.82
Multithreading Test	7.3	29.6	4.8	6.3	6.0	18.0
All Tests	3.8	7.8	4.2	2.9	4.0	5.4

The results above show that in general Hibernate with PostgreSQL server is more efficient than EclipseLink with Derby server in updating JPA entity objects in the database.

A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby database server (7.3) to the normalized speed of Hibernate with PostgreSQL database server (29.6) reveals that in that case, Hibernate with PostgreSQL server is 4.1 times faster than EclipseLink with Derby server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.026) to the normalized speed of EclipseLink with Derby database server (1.6) reveals that in that case, Hibernate with PostgreSQL server is 61.5 times slower than EclipseLink with Derby server.

Speed comparison of JPA database removal operations (normalized score, higher is better)

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server
Basic Person Test	2.8	5.3	3.9	4.2	3.3	4.8
Element Collection Test	1.2	0.020	0.55	stopped	0.87	0.0098
Inheritance Test	3.3	5.1	3.7	4.2	3.5	4.6
Indexing Test	4.9	9.5	3.5	6.3	4.2	7.9
Graph (Binary Tree) Test	0.51	0.012	0.50	0.012	0.51	0.012
Multithreading Test	4.8	23.3	5.7	21.8	5.3	22.5
All Tests	2.9	7.2	3.0	6.1	3.0	6.6

The results above show that in general Hibernate with PostgreSQL server is more efficient than EclipseLink with Derby server in deleting JPA entity objects from the database. Comparing the normalized speed of EclipseLink with Derby database server (3.0) to the normalized speed of Hibernate with PostgreSQL database server (6.6) reveals that in these tests, Hibernate with PostgreSQL server is 2.2 times faster than EclipseLink with Derby server.

A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby database server (4.8) to the normalized speed of Hibernate with PostgreSQL database server (23.3) reveals that in that case, Hibernate with PostgreSQL server is 4.9 times faster than EclipseLink with Derby server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.020) to the normalized speed of EclipseLink with Derby database server (1.2) reveals that in that case, Hibernate with PostgreSQL server is 60.0 times slower than EclipseLink with Derby server.

Comparison of JPA/Database speed - the averages (normalized score, higher is better)

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server	EclipseLink Derby server	Hibernate PostgreSQL server
Basic Person Test	12.5	15.7	5.6	5.6	9.1	10.7
Element Collection Test	8.4	2.8	1.4	0.35	4.9	1.6
Inheritance Test	7.7	15.0	6.3	6.9	7.0	10.9
Indexing Test	4.1	5.8	8.1	7.8	6.1	6.8
Graph (Binary Tree) Test	0.93	1.2	0.83	1.1	0.88	1.1
Multithreading Test	12.2	30.2	8.4	13.6	10.3	21.9
All Tests	7.9	12.1	5.2	6.0	6.6	9.1

The results above show that in general Hibernate with PostgreSQL server is more efficient than EclipseLink with Derby server in performing JPA database operations.

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (12.2) to the normalized speed of Hibernate with PostgreSQL database server (30.2) reveals that in that case, Hibernate with PostgreSQL server is 2.5 times faster than EclipseLink with Derby server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.35) to the normalized speed of EclipseLink with Derby database server (1.4) reveals that in that case, Hibernate with PostgreSQL server is 4.0 times slower than EclipseLink with Derby server.

JPA Performance Benchmark (JPAB)