Comparison of EclipseLink with H2 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 H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server
Basic Person Test	5.6	7.1	2.5	3.4	4.0	5.2
Element Collection Test	4.2	2.9	1.5	1.7	2.8	2.3
Inheritance Test	6.6	7.0	2.1	3.6	4.4	5.3
Indexing Test	9.7	9.3	4.1	6.1	6.9	7.7
Graph (Binary Tree) Test	4.7	3.0	3.5	2.9	4.1	2.9
Multithreading Test	10.2	31.7	4.0	13.9	7.1	22.8
All Tests	6.8	10.2	2.9	5.3	4.9	7.7

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server
Basic Person Test	5.5	5.5	8.2	11.5	6.8	8.5
Element Collection Test	3.2	0.025	4.2	0.017	3.7	0.021
Inheritance Test	4.7	5.2	10.1	14.0	7.4	9.6
Indexing Test	4.4	4.6	9.4	13.3	6.9	8.9
Graph (Binary Tree) Test	1.1	0.61	1.9	0.78	1.5	0.70
Multithreading Test	12.2	11.3	15.9	17.0	14.0	14.2
All Tests	5.2	4.5	8.3	9.4	6.7	7.0

The results above show that in general Hibernate with PostgreSQL server is slightly more efficient than EclipseLink with H2 server in retrieving JPA entity objects from the database.

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.017) to the normalized speed of EclipseLink with H2 database server (4.2) reveals that in that case, Hibernate with PostgreSQL server is 247 times slower than EclipseLink with H2 server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server
Basic Person Test	3.8	55.5	1.1	6.1	2.5	30.8
Element Collection Test	4.1	11.0	1.1	0.016	2.6	5.5
Inheritance Test	3.2	52.3	1.3	8.7	2.3	30.5
Indexing Test	3.0	0.050	8.0	8.8	5.5	4.4
Multithreading Test	1.1	55.2	1.0	9.2	1.1	32.2
All Tests	3.0	34.8	2.5	6.6	2.8	20.7

The results above show that in general Hibernate with PostgreSQL server is much more efficient than EclipseLink with H2 server in executing the tested JPA queries. Comparing the normalized speed of EclipseLink with H2 database server (2.8) to the normalized speed of Hibernate with PostgreSQL database server (20.7) reveals that in these tests, Hibernate with PostgreSQL server is 7.4 times faster than EclipseLink with H2 server.

A huge performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (1.1) to the normalized speed of Hibernate with PostgreSQL database server (55.2) reveals that in that case, Hibernate with PostgreSQL server is 50.2 times faster than EclipseLink with H2 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 H2 database server (1.1) reveals that in that case, Hibernate with PostgreSQL server is 68.8 times slower than EclipseLink with H2 server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server
Basic Person Test	4.5	5.3	2.2	2.7	3.4	4.0
Element Collection Test	3.8	0.067	2.4	0.026	3.1	0.046
Inheritance Test	4.4	5.4	3.0	3.8	3.7	4.6
Indexing Test	4.2	5.4	3.1	4.3	3.7	4.8
Graph (Binary Tree) Test	1.4	1.1	0.79	0.58	1.1	0.82
Multithreading Test	7.8	29.6	2.5	6.3	5.1	18.0
All Tests	4.3	7.8	2.3	2.9	3.3	5.4

The results above show that in general Hibernate with PostgreSQL server is more efficient than EclipseLink with H2 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 H2 database server (7.8) to the normalized speed of Hibernate with PostgreSQL database server (29.6) reveals that in that case, Hibernate with PostgreSQL server is 3.8 times faster than EclipseLink with H2 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 H2 database server (2.4) reveals that in that case, Hibernate with PostgreSQL server is 92.3 times slower than EclipseLink with H2 server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server
Basic Person Test	6.4	5.3	3.1	4.2	4.8	4.8
Element Collection Test	3.0	0.020	1.3	stopped	2.2	0.0098
Inheritance Test	5.6	5.1	2.8	4.2	4.2	4.6
Indexing Test	10.3	9.5	3.8	6.3	7.0	7.9
Graph (Binary Tree) Test	1.5	0.012	1.3	0.012	1.4	0.012
Multithreading Test	7.0	23.3	4.9	21.8	6.0	22.5
All Tests	5.6	7.2	2.9	6.1	4.3	6.6

The results above show that in general Hibernate with PostgreSQL server is more efficient than EclipseLink with H2 server 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 H2 database server (4.9) to the normalized speed of Hibernate with PostgreSQL database server (21.8) reveals that in that case, Hibernate with PostgreSQL server is 4.4 times faster than EclipseLink with H2 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 H2 database server (3.0) reveals that in that case, Hibernate with PostgreSQL server is 150 times slower than EclipseLink with H2 server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server	EclipseLink H2 server	Hibernate PostgreSQL server
Basic Person Test	5.2	15.7	3.4	5.6	4.3	10.7
Element Collection Test	3.6	2.8	2.1	0.35	2.9	1.6
Inheritance Test	4.9	15.0	3.9	6.9	4.4	10.9
Indexing Test	6.3	5.8	5.7	7.8	6.0	6.8
Graph (Binary Tree) Test	2.1	1.2	1.9	1.1	2.0	1.1
Multithreading Test	7.7	30.2	5.7	13.6	6.7	21.9
All Tests	5.1	12.1	3.8	6.0	4.5	9.1

The results above show that in general Hibernate with PostgreSQL server is more efficient than EclipseLink with H2 server in performing JPA database operations. Comparing the normalized speed of EclipseLink with H2 database server (4.5) to the normalized speed of Hibernate with PostgreSQL database server (9.1) reveals that in these tests, Hibernate with PostgreSQL server is 2.0 times faster than EclipseLink with H2 server.

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (7.7) to the normalized speed of Hibernate with PostgreSQL database server (30.2) reveals that in that case, Hibernate with PostgreSQL server is 3.9 times faster than EclipseLink with H2 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 H2 database server (2.1) reveals that in that case, Hibernate with PostgreSQL server is 6.0 times slower than EclipseLink with H2 server.

JPA Performance Benchmark (JPAB)