Comparison of EclipseLink with Derby embedded 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 embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server
Basic Person Test	5.5	7.1	3.7	3.4	4.6	5.2
Element Collection Test	3.0	2.9	1.7	1.7	2.4	2.3
Inheritance Test	5.3	7.0	3.5	3.6	4.4	5.3
Indexing Test	6.9	9.3	4.6	6.1	5.8	7.7
Graph (Binary Tree) Test	2.0	3.0	1.9	2.9	1.9	2.9
Multithreading Test	9.3	31.7	4.1	13.9	6.7	22.8
All Tests	5.3	10.2	3.2	5.3	4.3	7.7

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

A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (9.3) to the normalized speed of Hibernate with PostgreSQL database server (31.7) reveals that in that case, Hibernate with PostgreSQL server is 3.4 times faster than EclipseLink with Derby 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 PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server
Basic Person Test	16.4	5.5	58.7	11.5	37.5	8.5
Element Collection Test	7.5	0.025	13.3	0.017	10.4	0.021
Inheritance Test	17.1	5.2	58.9	14.0	38.0	9.6
Indexing Test	14.2	4.6	67.4	13.3	40.8	8.9
Graph (Binary Tree) Test	2.8	0.61	5.7	0.78	4.2	0.70
Multithreading Test	28.0	11.3	48.7	17.0	38.4	14.2
All Tests	14.3	4.5	42.1	9.4	28.2	7.0

The results above show that in general EclipseLink with Derby embedded is much more efficient than Hibernate with PostgreSQL server in retrieving JPA entity objects from the database. Comparing the normalized speed of Hibernate with PostgreSQL database server (7.0) to the normalized speed of EclipseLink with Derby embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 4.0 times faster than Hibernate with PostgreSQL server.

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 embedded database (13.3) reveals that in that case, EclipseLink with Derby embedded is 782 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 embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server
Basic Person Test	53.4	55.5	13.8	6.1	33.6	30.8
Element Collection Test	37.9	11.0	4.4	0.016	21.2	5.5
Inheritance Test	37.4	52.3	15.0	8.7	26.2	30.5
Indexing Test	7.6	0.050	49.3	8.8	28.4	4.4
Multithreading Test	41.2	55.2	6.1	9.2	23.6	32.2
All Tests	35.5	34.8	17.7	6.6	26.6	20.7

The results above show that in general EclipseLink with Derby embedded is slightly more efficient than Hibernate 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 Hibernate with PostgreSQL database server (0.016) to the normalized speed of EclipseLink with Derby embedded database (4.4) reveals that in that case, EclipseLink with Derby embedded is 275 times faster than Hibernate with PostgreSQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server
Basic Person Test	6.4	5.3	6.7	2.7	6.5	4.0
Element Collection Test	5.4	0.067	6.2	0.026	5.8	0.046
Inheritance Test	6.5	5.4	9.2	3.8	7.8	4.6
Indexing Test	7.3	5.4	11.1	4.3	9.2	4.8
Graph (Binary Tree) Test	2.8	1.1	1.7	0.58	2.2	0.82
Multithreading Test	21.3	29.6	5.0	6.3	13.1	18.0
All Tests	8.3	7.8	6.6	2.9	7.5	5.4

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

A huge performance gap has been detected 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 embedded database (6.2) reveals that in that case, EclipseLink with Derby embedded is 238 times faster than Hibernate with PostgreSQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server
Basic Person Test	4.6	5.3	4.7	4.2	4.6	4.8
Element Collection Test	2.5	0.020	1.4	stopped	1.9	0.0098
Inheritance Test	3.9	5.1	4.5	4.2	4.2	4.6
Indexing Test	6.2	9.5	3.8	6.3	5.0	7.9
Graph (Binary Tree) Test	1.1	0.012	1.0	0.012	1.1	0.012
Multithreading Test	6.2	23.3	5.8	21.8	6.0	22.5
All Tests	4.1	7.2	3.5	6.1	3.8	6.6

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

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

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 embedded database (2.5) reveals that in that case, Hibernate with PostgreSQL server is 125 times slower 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 PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server	EclipseLink Derby embedded	Hibernate PostgreSQL server
Basic Person Test	17.3	15.7	17.5	5.6	17.4	10.7
Element Collection Test	11.3	2.8	5.4	0.35	8.3	1.6
Inheritance Test	14.0	15.0	18.2	6.9	16.1	10.9
Indexing Test	8.4	5.8	27.2	7.8	17.8	6.8
Graph (Binary Tree) Test	2.2	1.2	2.6	1.1	2.4	1.1
Multithreading Test	21.2	30.2	13.9	13.6	17.6	21.9
All Tests	12.7	12.1	14.5	6.0	13.6	9.1

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

A huge performance gap has been detected 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 embedded database (5.4) reveals that in that case, EclipseLink with Derby embedded is 15.4 times faster than Hibernate with PostgreSQL server.

JPA Performance Benchmark (JPAB)