• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with PostgreSQL server 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 PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded
Basic Person Test	7.3	0.083	4.2	1.0	5.8	0.55
Element Collection Test	3.1	0.067	1.9	0.69	2.5	0.38
Inheritance Test	6.9	0.080	5.0	0.99	5.9	0.54
Indexing Test	10.0	0.098	6.8	1.0	8.4	0.55
Graph (Binary Tree) Test	3.5	0.27	3.3	0.96	3.4	0.61
Multithreading Test	31.8	failed	14.5	failed	23.1	failed
All Tests	10.4	0.12	6.0	0.93	8.2	0.53

Hibernate with SQLite embedded has failed in 2 tests (see exceptions).

The results above show that in general EclipseLink with PostgreSQL server 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 PostgreSQL database server (8.2) reveals that in these tests, EclipseLink with PostgreSQL server is 15.5 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 PostgreSQL database server (10.0) reveals that in that case, EclipseLink with PostgreSQL server is 102 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 PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded
Basic Person Test	6.8	1.8	17.2	1.3	12.0	1.5
Element Collection Test	0.026	0.0008	0.020	failed	0.023	0.0008
Inheritance Test	6.0	2.4	19.7	1.4	12.9	1.9
Indexing Test	5.6	1.9	19.5	2.3	12.6	2.1
Graph (Binary Tree) Test	0.47	0.56	0.61	0.88	0.54	0.72
Multithreading Test	13.5	failed	27.8	failed	20.6	failed
All Tests	5.4	1.3	14.1	1.5	9.8	1.4

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general EclipseLink with PostgreSQL server 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 PostgreSQL database server (9.8) reveals that in these tests, EclipseLink with PostgreSQL server is 7.0 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 PostgreSQL database server (0.026) reveals that in that case, EclipseLink with PostgreSQL server is 32.5 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 PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded
Basic Person Test	55.5	1.1	7.8	0.22	31.6	0.65
Element Collection Test	15.4	0.39	0.028	failed	7.7	0.39
Inheritance Test	54.9	0.53	11.5	0.28	33.2	0.40
Indexing Test	0.077	0.0011	10.0	0.43	5.1	0.21
Multithreading Test	55.3	failed	12.0	failed	33.7	failed
All Tests	36.2	0.50	8.3	0.31	22.3	0.42

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general EclipseLink with PostgreSQL server 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 PostgreSQL database server (22.3) reveals that in these tests, EclipseLink with PostgreSQL server is 53.1 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.53) to the normalized speed of EclipseLink with PostgreSQL database server (54.9) reveals that in that case, EclipseLink with PostgreSQL server is 104 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 PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded
Basic Person Test	6.2	0.076	4.1	0.65	5.1	0.37
Element Collection Test	0.080	0.0022	0.028	failed	0.054	0.0022
Inheritance Test	6.4	0.079	6.1	0.97	6.2	0.53
Indexing Test	6.5	0.057	7.0	0.54	6.8	0.30
Graph (Binary Tree) Test	0.90	0.26	0.50	0.42	0.70	0.34
Multithreading Test	36.0	failed	9.1	failed	22.5	failed
All Tests	9.3	0.094	4.5	0.65	6.9	0.34

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general EclipseLink with PostgreSQL server 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 PostgreSQL database server (6.9) reveals that in these tests, EclipseLink with PostgreSQL server is 20.3 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.057) to the normalized speed of EclipseLink with PostgreSQL database server (6.5) reveals that in that case, EclipseLink with PostgreSQL server is 114 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 PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded
Basic Person Test	5.7	0.061	5.7	0.91	5.7	0.49
Element Collection Test	0.025	0.0007	stopped	failed	0.012	0.0007
Inheritance Test	5.5	0.058	5.4	0.90	5.4	0.48
Indexing Test	10.4	0.079	10.0	0.54	10.2	0.31
Graph (Binary Tree) Test	0.016	0.24	0.013	0.80	0.015	0.52
Multithreading Test	26.3	failed	16.8	failed	21.6	failed
All Tests	8.0	0.088	6.3	0.79	7.2	0.40

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general EclipseLink with PostgreSQL server 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 PostgreSQL database server (7.2) reveals that in these tests, EclipseLink with PostgreSQL server is 18.0 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.079) to the normalized speed of EclipseLink with PostgreSQL database server (10.4) reveals that in that case, EclipseLink with PostgreSQL server is 132 times faster than Hibernate with SQLite embedded.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, 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 Hibernate with SQLite embedded database (0.80) reveals that in that case, EclipseLink with PostgreSQL server is 61.5 times slower than Hibernate with SQLite embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded	EclipseLink PostgreSQL server	Hibernate SQLite embedded
Basic Person Test	16.3	0.63	7.8	0.81	12.1	0.72
Element Collection Test	3.7	0.092	0.40	0.69	2.1	0.19
Inheritance Test	15.9	0.63	9.5	0.91	12.7	0.77
Indexing Test	6.5	0.42	10.7	0.96	8.6	0.69
Graph (Binary Tree) Test	1.2	0.33	1.1	0.77	1.2	0.55
Multithreading Test	32.6	failed	16.0	failed	24.3	failed
All Tests	13.1	0.42	7.8	0.86	10.5	0.62

The results above show that in general EclipseLink with PostgreSQL server 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 PostgreSQL database server (10.5) reveals that in these tests, EclipseLink with PostgreSQL server is 16.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 PostgreSQL database server (3.7) reveals that in that case, EclipseLink with PostgreSQL server is 40.2 times faster than Hibernate with SQLite embedded.

Other Head to Head DBMS/JPA Comparisons

JPA Performance Benchmark - Copyright © 2010, 2011, 2012 ObjectDB Software Ltd. - All rights reserved.
The benchmark program is released as open source under the GPL license.