• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with Derby 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 Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded
Basic Person Test	3.8	0.083	3.1	1.0	3.4	0.55
Element Collection Test	2.2	0.067	1.5	0.69	1.8	0.38
Inheritance Test	3.9	0.080	2.9	0.99	3.4	0.54
Indexing Test	5.2	0.098	4.3	1.0	4.7	0.55
Graph (Binary Tree) Test	1.9	0.27	1.7	0.96	1.8	0.61
Multithreading Test	6.1	failed	3.9	failed	5.0	failed
All Tests	3.8	0.12	2.9	0.93	3.4	0.53

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

The results above show that in general EclipseLink with Derby 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 Derby database server (3.4) reveals that in these tests, EclipseLink with Derby server is 6.4 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 Derby database server (5.2) reveals that in that case, EclipseLink with Derby server is 53.1 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 Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded
Basic Person Test	6.4	1.8	11.3	1.3	8.8	1.5
Element Collection Test	1.8	0.0008	2.4	failed	2.1	0.0008
Inheritance Test	3.7	2.4	12.9	1.4	8.3	1.9
Indexing Test	3.6	1.9	12.8	2.3	8.2	2.1
Graph (Binary Tree) Test	0.61	0.56	0.73	0.88	0.67	0.72
Multithreading Test	8.5	failed	19.8	failed	14.1	failed
All Tests	4.1	1.3	10.0	1.5	7.0	1.4

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

The results above show that in general EclipseLink with Derby 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 Derby database server (7.0) reveals that in these tests, EclipseLink with Derby server is 5.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 Derby database server (1.8) reveals that in that case, EclipseLink with Derby server is 2,250 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 Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded
Basic Person Test	45.8	1.1	5.3	0.22	25.6	0.65
Element Collection Test	35.2	0.39	0.99	failed	18.1	0.39
Inheritance Test	23.1	0.53	5.9	0.28	14.5	0.40
Indexing Test	2.5	0.0011	12.2	0.43	7.4	0.21
Multithreading Test	34.3	failed	7.7	failed	21.0	failed
All Tests	28.2	0.50	6.4	0.31	17.3	0.42

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

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

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0011) to the normalized speed of EclipseLink with Derby database server (2.5) reveals that in that case, EclipseLink with Derby server is 2,273 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 Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded
Basic Person Test	3.9	0.076	4.4	0.65	4.1	0.37
Element Collection Test	1.7	0.0022	1.6	failed	1.6	0.0022
Inheritance Test	4.6	0.079	6.1	0.97	5.3	0.53
Indexing Test	4.5	0.057	7.6	0.54	6.1	0.30
Graph (Binary Tree) Test	0.70	0.26	0.42	0.42	0.56	0.34
Multithreading Test	7.3	failed	4.8	failed	6.0	failed
All Tests	3.8	0.094	4.2	0.65	4.0	0.34

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

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0022) to the normalized speed of EclipseLink with Derby database server (1.7) reveals that in that case, EclipseLink with Derby server is 773 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 Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded
Basic Person Test	2.8	0.061	3.9	0.91	3.3	0.49
Element Collection Test	1.2	0.0007	0.55	failed	0.87	0.0007
Inheritance Test	3.3	0.058	3.7	0.90	3.5	0.48
Indexing Test	4.9	0.079	3.5	0.54	4.2	0.31
Graph (Binary Tree) Test	0.51	0.24	0.50	0.80	0.51	0.52
Multithreading Test	4.8	failed	5.7	failed	5.3	failed
All Tests	2.9	0.088	3.0	0.79	3.0	0.40

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

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0007) to the normalized speed of EclipseLink with Derby database server (1.2) reveals that in that case, EclipseLink with Derby server is 1,714 times faster 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 Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded	EclipseLink Derby server	Hibernate SQLite embedded
Basic Person Test	12.5	0.63	5.6	0.81	9.1	0.72
Element Collection Test	8.4	0.092	1.4	0.69	4.9	0.19
Inheritance Test	7.7	0.63	6.3	0.91	7.0	0.77
Indexing Test	4.1	0.42	8.1	0.96	6.1	0.69
Graph (Binary Tree) Test	0.93	0.33	0.83	0.77	0.88	0.55
Multithreading Test	12.2	failed	8.4	failed	10.3	failed
All Tests	7.9	0.42	5.2	0.86	6.6	0.62

The results above show that in general EclipseLink with Derby 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 Derby database server (6.6) reveals that in these tests, EclipseLink with Derby server is 10.6 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 Derby database server (8.4) reveals that in that case, EclipseLink with Derby server is 91.3 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.