• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of Hibernate with Derby embedded vs EclipseLink 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
	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded
Basic Person Test	5.9	0.074	3.8	0.90	4.9	0.49
Element Collection Test	2.9	0.061	1.8	0.65	2.3	0.36
Inheritance Test	5.3	0.083	3.7	0.82	4.5	0.45
Indexing Test	7.0	0.11	4.8	1.6	5.9	0.87
Graph (Binary Tree) Test	1.9	0.24	1.7	0.91	1.8	0.57
Multithreading Test	10.5	0.10	3.7	2.1	7.1	1.1
All Tests	5.6	0.11	3.3	1.2	4.4	0.64

The results above show that in general Hibernate with Derby embedded is much more efficient than EclipseLink with SQLite embedded in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.64) to the normalized speed of Hibernate with Derby embedded database (4.4) reveals that in these tests, Hibernate with Derby embedded is 6.9 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.10) to the normalized speed of Hibernate with Derby embedded database (10.5) reveals that in that case, Hibernate with Derby embedded is 105 times faster than EclipseLink with SQLite embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded
Basic Person Test	14.2	failed	16.4	failed	15.3	failed
Element Collection Test	4.4	0.0007	4.9	failed	4.6	0.0007
Inheritance Test	10.3	failed	18.6	failed	14.4	failed
Indexing Test	10.0	failed	16.4	failed	13.2	failed
Graph (Binary Tree) Test	2.6	failed	3.0	failed	2.8	failed
Multithreading Test	19.3	failed	19.3	failed	19.3	failed
All Tests	10.1	0.0007	13.1	failed	11.6	0.0007

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded
Basic Person Test	49.3	1.2	6.8	failed	28.1	1.2
Element Collection Test	37.6	0.29	2.7	failed	20.1	0.29
Inheritance Test	24.1	0.69	7.6	failed	15.9	0.69
Indexing Test	5.3	0.0008	14.8	failed	10.1	0.0008
Multithreading Test	39.7	failed	6.1	failed	22.9	failed
All Tests	31.2	0.55	7.6	failed	19.4	0.55

EclipseLink with SQLite embedded has failed in 6 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded
Basic Person Test	4.5	failed	3.2	failed	3.8	failed
Element Collection Test	3.9	0.0016	3.1	failed	3.5	0.0016
Inheritance Test	4.6	failed	4.5	failed	4.5	failed
Indexing Test	4.6	failed	5.5	failed	5.1	failed
Graph (Binary Tree) Test	2.7	failed	1.2	failed	2.0	failed
Multithreading Test	11.6	failed	2.6	failed	7.1	failed
All Tests	5.3	0.0016	3.3	failed	4.3	0.0016

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded
Basic Person Test	3.8	failed	4.2	failed	4.0	failed
Element Collection Test	2.3	0.0006	1.5	failed	1.9	0.0006
Inheritance Test	4.0	failed	4.3	failed	4.2	failed
Indexing Test	5.5	failed	3.6	failed	4.6	failed
Graph (Binary Tree) Test	0.74	failed	0.96	failed	0.85	failed
Multithreading Test	5.6	failed	4.9	failed	5.3	failed
All Tests	3.7	0.0006	3.3	failed	3.5	0.0006

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded
Basic Person Test	52.7	79.4	52.7	79.4	52.7	79.4
Element Collection Test	42.3	74.5	42.3	74.5	42.3	74.5
Inheritance Test	49.2	75.0	49.2	75.0	49.2	75.0
Indexing Test	53.0	92.9	53.9	94.5	53.4	93.7
Graph (Binary Tree) Test	13.1	60.6	9.8	48.4	11.5	54.5
Multithreading Test	49.3	100	8.8	100	29.0	100
All Tests	43.3	80.4	36.1	78.6	39.7	79.5

The results above show that in general EclipseLink with SQLite embedded is more efficient than Hibernate with Derby embedded in using disk space. Comparing the normalized score of Hibernate with Derby embedded database (39.7) to the normalized score of EclipseLink with SQLite embedded database (79.5) reveals that in these tests, EclipseLink with SQLite embedded is 2.0 times more efficient than Hibernate with Derby embedded.

A huge gap has been detected when using multithreading with large transaction size. Comparing the normalized score of Hibernate with Derby embedded database (8.8) to the normalized score of EclipseLink with SQLite embedded database (100) reveals that in that case, EclipseLink with SQLite embedded is 11.4 times more efficient than Hibernate with Derby embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded	Hibernate Derby embedded	EclipseLink SQLite embedded
Basic Person Test	15.5	0.66	6.9	0.90	11.2	0.74
Element Collection Test	10.2	0.070	2.8	0.65	6.5	0.17
Inheritance Test	9.7	0.38	7.7	0.82	8.7	0.53
Indexing Test	6.5	0.058	9.0	1.6	7.8	0.58
Graph (Binary Tree) Test	2.0	0.24	1.7	0.91	1.8	0.57
Multithreading Test	17.3	0.10	7.3	2.1	12.3	1.1
All Tests	10.5	0.22	6.1	1.2	8.3	0.52

The results above show that in general Hibernate with Derby embedded is much more efficient than EclipseLink with SQLite embedded in performing JPA database operations. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.52) to the normalized speed of Hibernate with Derby embedded database (8.3) reveals that in these tests, Hibernate with Derby embedded is 16.0 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.10) to the normalized speed of Hibernate with Derby embedded database (17.3) reveals that in that case, Hibernate with Derby embedded is 173 times faster than EclipseLink 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.