• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of Hibernate with SQLite embedded vs EclipseLink with Derby 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 SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded
Basic Person Test	0.083	5.5	1.0	3.7	0.55	4.6
Element Collection Test	0.067	3.0	0.69	1.7	0.38	2.4
Inheritance Test	0.080	5.3	0.99	3.5	0.54	4.4
Indexing Test	0.098	6.9	1.0	4.6	0.55	5.8
Graph (Binary Tree) Test	0.27	2.0	0.96	1.9	0.61	1.9
Multithreading Test	failed	9.3	failed	4.1	failed	6.7
All Tests	0.12	5.3	0.93	3.2	0.53	4.3

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (4.3) reveals that in these tests, EclipseLink with Derby embedded is 8.1 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 embedded database (6.9) reveals that in that case, EclipseLink with Derby embedded is 70.4 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
	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded
Basic Person Test	1.8	16.4	1.3	58.7	1.5	37.5
Element Collection Test	0.0008	7.5	failed	13.3	0.0008	10.4
Inheritance Test	2.4	17.1	1.4	58.9	1.9	38.0
Indexing Test	1.9	14.2	2.3	67.4	2.1	40.8
Graph (Binary Tree) Test	0.56	2.8	0.88	5.7	0.72	4.2
Multithreading Test	failed	28.0	failed	48.7	failed	38.4
All Tests	1.3	14.3	1.5	42.1	1.4	28.2

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 20.1 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 embedded database (7.5) reveals that in that case, EclipseLink with Derby embedded is 9,375 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
	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded
Basic Person Test	1.1	53.4	0.22	13.8	0.65	33.6
Element Collection Test	0.39	37.9	failed	4.4	0.39	21.2
Inheritance Test	0.53	37.4	0.28	15.0	0.40	26.2
Indexing Test	0.0011	7.6	0.43	49.3	0.21	28.4
Multithreading Test	failed	41.2	failed	6.1	failed	23.6
All Tests	0.50	35.5	0.31	17.7	0.42	26.6

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (26.6) reveals that in these tests, EclipseLink with Derby embedded is 63.3 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 embedded database (7.6) reveals that in that case, EclipseLink with Derby embedded is 6,909 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
	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded
Basic Person Test	0.076	6.4	0.65	6.7	0.37	6.5
Element Collection Test	0.0022	5.4	failed	6.2	0.0022	5.8
Inheritance Test	0.079	6.5	0.97	9.2	0.53	7.8
Indexing Test	0.057	7.3	0.54	11.1	0.30	9.2
Graph (Binary Tree) Test	0.26	2.8	0.42	1.7	0.34	2.2
Multithreading Test	failed	21.3	failed	5.0	failed	13.1
All Tests	0.094	8.3	0.65	6.6	0.34	7.5

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (7.5) reveals that in these tests, EclipseLink with Derby embedded is 22.1 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 embedded database (5.4) reveals that in that case, EclipseLink with Derby embedded is 2,455 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
	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded
Basic Person Test	0.061	4.6	0.91	4.7	0.49	4.6
Element Collection Test	0.0007	2.5	failed	1.4	0.0007	1.9
Inheritance Test	0.058	3.9	0.90	4.5	0.48	4.2
Indexing Test	0.079	6.2	0.54	3.8	0.31	5.0
Graph (Binary Tree) Test	0.24	1.1	0.80	1.0	0.52	1.1
Multithreading Test	failed	6.2	failed	5.8	failed	6.0
All Tests	0.088	4.1	0.79	3.5	0.40	3.8

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

The results above show that in general EclipseLink with Derby embedded 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 embedded database (3.8) reveals that in these tests, EclipseLink with Derby embedded is 9.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 embedded database (2.5) reveals that in that case, EclipseLink with Derby embedded is 3,571 times faster than Hibernate with SQLite embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded
Basic Person Test	90.2	51.1	90.2	51.0	90.2	51.1
Element Collection Test	82.0	38.5	82.0	39.4	82.0	38.9
Inheritance Test	80.5	48.0	80.5	47.9	80.5	48.0
Indexing Test	93.4	51.6	94.8	52.3	94.1	52.0
Graph (Binary Tree) Test	67.9	13.4	50.9	11.7	59.4	12.6
Multithreading Test	failed	52.6	failed	8.4	failed	30.5
All Tests	82.8	42.5	79.7	35.1	81.2	38.8

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

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

A large gap has been detected when using graphs of objects with small transaction size. Comparing the normalized score of EclipseLink with Derby embedded database (13.4) to the normalized score of Hibernate with SQLite embedded database (67.9) reveals that in that case, Hibernate with SQLite embedded is 5.1 times more efficient 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
	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded	Hibernate SQLite embedded	EclipseLink Derby embedded
Basic Person Test	0.63	17.3	0.81	17.5	0.72	17.4
Element Collection Test	0.092	11.3	0.69	5.4	0.19	8.3
Inheritance Test	0.63	14.0	0.91	18.2	0.77	16.1
Indexing Test	0.42	8.4	0.96	27.2	0.69	17.8
Graph (Binary Tree) Test	0.33	2.2	0.77	2.6	0.55	2.4
Multithreading Test	failed	21.2	failed	13.9	failed	17.6
All Tests	0.42	12.7	0.86	14.5	0.62	13.6

The results above show that in general EclipseLink with Derby embedded 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 embedded database (13.6) reveals that in these tests, EclipseLink with Derby embedded is 21.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 Derby embedded database (11.3) reveals that in that case, EclipseLink with Derby embedded is 123 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.