Comparison of Hibernate with Derby server vs EclipseLink with H2 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 server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded
Basic Person Test	3.8	25.1	3.0	8.9	3.4	17.0
Element Collection Test	2.0	20.4	1.3	8.0	1.7	14.2
Inheritance Test	3.4	28.7	3.0	8.7	3.2	18.7
Indexing Test	4.8	37.6	4.1	14.0	4.4	25.8
Graph (Binary Tree) Test	1.8	17.7	1.6	14.7	1.7	16.2
Multithreading Test	6.9	30.3	3.9	11.4	5.4	20.8
All Tests	3.8	26.6	2.8	10.9	3.3	18.8

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with Derby database server (2.0) to the normalized speed of EclipseLink with H2 embedded database (20.4) reveals that in that case, EclipseLink with H2 embedded is 10.2 times faster than Hibernate with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded
Basic Person Test	3.8	30.4	8.4	29.1	6.1	29.7
Element Collection Test	1.0	19.6	1.0	27.6	1.0	23.6
Inheritance Test	3.5	33.8	9.7	39.8	6.6	36.8
Indexing Test	3.2	22.2	9.5	41.3	6.4	31.8
Graph (Binary Tree) Test	0.91	16.0	1.2	20.0	1.1	18.0
Multithreading Test	7.8	33.7	13.4	29.0	10.6	31.4
All Tests	3.4	25.9	7.2	31.1	5.3	28.5

The results above show that in general EclipseLink with H2 embedded is much more efficient than Hibernate with Derby server in retrieving JPA entity objects from the database. Comparing the normalized speed of Hibernate with Derby database server (5.3) to the normalized speed of EclipseLink with H2 embedded database (28.5) reveals that in these tests, EclipseLink with H2 embedded is 5.4 times faster than Hibernate with Derby server.

A huge performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of Hibernate with Derby database server (1.0) to the normalized speed of EclipseLink with H2 embedded database (27.6) reveals that in that case, EclipseLink with H2 embedded is 27.6 times faster than Hibernate with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded
Basic Person Test	34.0	4.4	4.1	1.4	19.1	2.9
Element Collection Test	33.8	4.1	0.64	2.4	17.2	3.2
Inheritance Test	20.5	3.4	5.0	2.0	12.8	2.7
Indexing Test	2.0	13.0	9.2	22.8	5.6	17.9
Multithreading Test	36.2	1.0	5.1	0.67	20.6	0.85
All Tests	25.3	5.2	4.8	5.9	15.1	5.5

The results above show that in general Hibernate with Derby server is more efficient than EclipseLink with H2 embedded in executing the tested JPA queries. Comparing the normalized speed of EclipseLink with H2 embedded database (5.5) to the normalized speed of Hibernate with Derby database server (15.1) reveals that in these tests, Hibernate with Derby server is 2.7 times faster than EclipseLink with H2 embedded.

A huge performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of EclipseLink with H2 embedded database (1.0) to the normalized speed of Hibernate with Derby database server (36.2) reveals that in that case, Hibernate with Derby server is 36.2 times faster than EclipseLink with H2 embedded.

On the other hand, Hibernate with Derby server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of Hibernate with Derby database server (2.0) to the normalized speed of EclipseLink with H2 embedded database (13.0) reveals that in that case, Hibernate with Derby server is 6.5 times slower than EclipseLink with H2 embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded
Basic Person Test	2.9	16.6	2.5	7.6	2.7	12.1
Element Collection Test	2.3	15.3	1.5	10.5	1.9	12.9
Inheritance Test	2.9	15.7	3.5	9.8	3.2	12.7
Indexing Test	3.0	12.1	4.2	9.9	3.6	11.0
Graph (Binary Tree) Test	1.2	13.7	0.58	7.0	0.91	10.3
Multithreading Test	6.8	20.9	2.5	4.2	4.6	12.6
All Tests	3.2	15.7	2.5	8.2	2.8	12.0

The results above show that in general EclipseLink with H2 embedded is much more efficient than Hibernate with Derby server in updating JPA entity objects in the database. Comparing the normalized speed of Hibernate with Derby database server (2.8) to the normalized speed of EclipseLink with H2 embedded database (12.0) reveals that in these tests, EclipseLink with H2 embedded is 4.3 times faster than Hibernate with Derby server.

A huge performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of Hibernate with Derby database server (0.58) to the normalized speed of EclipseLink with H2 embedded database (7.0) reveals that in that case, EclipseLink with H2 embedded is 12.1 times faster than Hibernate with Derby server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded
Basic Person Test	2.9	35.1	3.5	19.6	3.2	27.4
Element Collection Test	1.7	19.3	0.87	8.5	1.3	13.9
Inheritance Test	2.9	36.0	3.6	14.0	3.2	25.0
Indexing Test	3.7	42.5	3.6	19.2	3.7	30.9
Graph (Binary Tree) Test	0.69	12.2	0.70	14.4	0.70	13.3
Multithreading Test	6.2	54.4	5.1	25.8	5.6	40.1
All Tests	3.0	33.3	2.9	16.9	3.0	25.1

The results above show that in general EclipseLink with H2 embedded is much more efficient than Hibernate with Derby server in deleting JPA entity objects from the database. Comparing the normalized speed of Hibernate with Derby database server (3.0) to the normalized speed of EclipseLink with H2 embedded database (25.1) reveals that in these tests, EclipseLink with H2 embedded is 8.4 times faster than Hibernate with Derby server.

A huge performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of Hibernate with Derby database server (0.70) to the normalized speed of EclipseLink with H2 embedded database (14.4) reveals that in that case, EclipseLink with H2 embedded is 20.6 times faster than Hibernate with Derby server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded	Hibernate Derby server	EclipseLink H2 embedded
Basic Person Test	9.5	22.3	4.3	13.3	6.9	17.8
Element Collection Test	8.2	15.7	1.1	11.4	4.6	13.6
Inheritance Test	6.6	23.5	5.0	14.9	5.8	19.2
Indexing Test	3.3	25.5	6.1	21.5	4.7	23.5
Graph (Binary Tree) Test	1.2	14.9	1.0	14.0	1.1	14.5
Multithreading Test	12.8	28.1	6.0	14.2	9.4	21.1
All Tests	7.1	21.9	4.0	14.9	5.6	18.4

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

A huge performance gap has been detected when using graphs of objects with large transaction/retrieval size. Comparing the normalized speed of Hibernate with Derby database server (1.0) to the normalized speed of EclipseLink with H2 embedded database (14.0) reveals that in that case, EclipseLink with H2 embedded is 14.0 times faster than Hibernate with Derby server.

JPA Performance Benchmark (JPAB)