Comparison of Hibernate with Derby 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 Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded
Basic Person Test	5.9	5.5	3.8	3.7	4.9	4.6
Element Collection Test	2.9	3.0	1.8	1.7	2.3	2.4
Inheritance Test	5.3	5.3	3.7	3.5	4.5	4.4
Indexing Test	7.0	6.9	4.8	4.6	5.9	5.8
Graph (Binary Tree) Test	1.9	2.0	1.7	1.9	1.8	1.9
Multithreading Test	10.5	9.3	3.7	4.1	7.1	6.7
All Tests	5.6	5.3	3.3	3.2	4.4	4.3

The results above show that in general Hibernate with Derby embedded is slightly more efficient than EclipseLink with Derby embedded in persisting JPA entity objects to the database.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded
Basic Person Test	14.2	16.4	16.4	58.7	15.3	37.5
Element Collection Test	4.4	7.5	4.9	13.3	4.6	10.4
Inheritance Test	10.3	17.1	18.6	58.9	14.4	38.0
Indexing Test	10.0	14.2	16.4	67.4	13.2	40.8
Graph (Binary Tree) Test	2.6	2.8	3.0	5.7	2.8	4.2
Multithreading Test	19.3	28.0	19.3	48.7	19.3	38.4
All Tests	10.1	14.3	13.1	42.1	11.6	28.2

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

A large performance gap has been detected when using database indexes with large retrieval size. Comparing the normalized speed of Hibernate with Derby embedded database (16.4) to the normalized speed of EclipseLink with Derby embedded database (67.4) reveals that in that case, EclipseLink with Derby embedded is 4.1 times faster than Hibernate with Derby embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded
Basic Person Test	49.3	53.4	6.8	13.8	28.1	33.6
Element Collection Test	37.6	37.9	2.7	4.4	20.1	21.2
Inheritance Test	24.1	37.4	7.6	15.0	15.9	26.2
Indexing Test	5.3	7.6	14.8	49.3	10.1	28.4
Multithreading Test	39.7	41.2	6.1	6.1	22.9	23.6
All Tests	31.2	35.5	7.6	17.7	19.4	26.6

The results above show that in general EclipseLink with Derby embedded is more efficient than Hibernate with Derby embedded in executing the tested JPA queries.

A large performance gap has been detected when using database indexes with large retrieval size. Comparing the normalized speed of Hibernate with Derby embedded database (14.8) to the normalized speed of EclipseLink with Derby embedded database (49.3) reveals that in that case, EclipseLink with Derby embedded is 3.3 times faster than Hibernate with Derby embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded
Basic Person Test	4.5	6.4	3.2	6.7	3.8	6.5
Element Collection Test	3.9	5.4	3.1	6.2	3.5	5.8
Inheritance Test	4.6	6.5	4.5	9.2	4.5	7.8
Indexing Test	4.6	7.3	5.5	11.1	5.1	9.2
Graph (Binary Tree) Test	2.7	2.8	1.2	1.7	2.0	2.2
Multithreading Test	11.6	21.3	2.6	5.0	7.1	13.1
All Tests	5.3	8.3	3.3	6.6	4.3	7.5

The results above show that in general EclipseLink with Derby embedded is more efficient than Hibernate with Derby embedded in updating JPA entity objects in the database.

A large performance gap has been detected when using simple basic entities with large transaction size. Comparing the normalized speed of Hibernate with Derby embedded database (3.2) to the normalized speed of EclipseLink with Derby embedded database (6.7) reveals that in that case, EclipseLink with Derby embedded is 2.1 times faster than Hibernate with Derby embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded
Basic Person Test	3.8	4.6	4.2	4.7	4.0	4.6
Element Collection Test	2.3	2.5	1.5	1.4	1.9	1.9
Inheritance Test	4.0	3.9	4.3	4.5	4.2	4.2
Indexing Test	5.5	6.2	3.6	3.8	4.6	5.0
Graph (Binary Tree) Test	0.74	1.1	0.96	1.0	0.85	1.1
Multithreading Test	5.6	6.2	4.9	5.8	5.3	6.0
All Tests	3.7	4.1	3.3	3.5	3.5	3.8

The results above show that in general EclipseLink with Derby embedded is slightly more efficient than Hibernate with Derby embedded in deleting JPA entity objects from the database.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded
Basic Person Test	52.7	51.1	52.7	51.0	52.7	51.1
Element Collection Test	42.3	38.5	42.3	39.4	42.3	38.9
Inheritance Test	49.2	48.0	49.2	47.9	49.2	48.0
Indexing Test	53.0	51.6	53.9	52.3	53.4	52.0
Graph (Binary Tree) Test	13.1	13.4	9.8	11.7	11.5	12.6
Multithreading Test	49.3	52.6	8.8	8.4	29.0	30.5
All Tests	43.3	42.5	36.1	35.1	39.7	38.8

The results above show that in general Hibernate with Derby embedded is slightly more efficient than EclipseLink with Derby embedded in using disk space.

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 Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded	Hibernate Derby embedded	EclipseLink Derby embedded
Basic Person Test	15.5	17.3	6.9	17.5	11.2	17.4
Element Collection Test	10.2	11.3	2.8	5.4	6.5	8.3
Inheritance Test	9.7	14.0	7.7	18.2	8.7	16.1
Indexing Test	6.5	8.4	9.0	27.2	7.8	17.8
Graph (Binary Tree) Test	2.0	2.2	1.7	2.6	1.8	2.4
Multithreading Test	17.3	21.2	7.3	13.9	12.3	17.6
All Tests	10.5	12.7	6.1	14.5	8.3	13.6

The results above show that in general EclipseLink with Derby embedded is more efficient than Hibernate with Derby embedded in performing JPA database operations.

A large performance gap has been detected when using database indexes with large transaction/retrieval size. Comparing the normalized speed of Hibernate with Derby embedded database (9.0) to the normalized speed of EclipseLink with Derby embedded database (27.2) reveals that in that case, EclipseLink with Derby embedded is 3.0 times faster than Hibernate with Derby embedded.

JPA Performance Benchmark (JPAB)