Comparison of Hibernate with Derby server vs EclipseLink with MySQL server

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 MySQL server	Hibernate Derby server	EclipseLink MySQL server	Hibernate Derby server	EclipseLink MySQL server
Basic Person Test	3.8	3.6	3.0	1.5	3.4	2.6
Element Collection Test	2.0	1.5	1.3	0.69	1.7	1.1
Inheritance Test	3.4	3.5	3.0	1.4	3.2	2.4
Indexing Test	4.8	5.3	4.1	2.5	4.4	3.9
Graph (Binary Tree) Test	1.8	1.7	1.6	1.3	1.7	1.5
Multithreading Test	6.9	7.2	3.9	2.4	5.4	4.8
All Tests	3.8	3.8	2.8	1.6	3.3	2.7

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

A large performance gap has been detected when using class inheritance in the object model with large transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (1.4) to the normalized speed of Hibernate with Derby database server (3.0) reveals that in that case, Hibernate with Derby server is 2.1 times faster than EclipseLink with MySQL 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 MySQL server	Hibernate Derby server	EclipseLink MySQL server	Hibernate Derby server	EclipseLink MySQL server
Basic Person Test	3.8	0.43	8.4	15.5	6.1	8.0
Element Collection Test	1.0	0.16	1.0	1.4	1.0	0.78
Inheritance Test	3.5	0.39	9.7	17.6	6.6	9.0
Indexing Test	3.2	0.43	9.5	16.6	6.4	8.5
Graph (Binary Tree) Test	0.91	0.53	1.2	0.76	1.1	0.65
Multithreading Test	7.8	0.19	13.4	11.0	10.6	5.6
All Tests	3.4	0.35	7.2	10.5	5.3	5.4

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

On the other hand, EclipseLink with MySQL server is slower, for instance, when using multithreading with small retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.19) to the normalized speed of Hibernate with Derby database server (7.8) reveals that in that case, EclipseLink with MySQL server is 41.1 times slower 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 MySQL server	Hibernate Derby server	EclipseLink MySQL server	Hibernate Derby server	EclipseLink MySQL server
Basic Person Test	34.0	1.5	4.1	0.44	19.1	0.95
Element Collection Test	33.8	1.4	0.64	0.43	17.2	0.92
Inheritance Test	20.5	1.1	5.0	0.61	12.8	0.86
Indexing Test	2.0	0.26	9.2	0.52	5.6	0.39
Multithreading Test	36.2	1.9	5.1	0.72	20.6	1.3
All Tests	25.3	1.2	4.8	0.54	15.1	0.88

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

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (1.4) to the normalized speed of Hibernate with Derby database server (33.8) reveals that in that case, Hibernate with Derby server is 24.1 times faster than EclipseLink with MySQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby server	EclipseLink MySQL server	Hibernate Derby server	EclipseLink MySQL server	Hibernate Derby server	EclipseLink MySQL server
Basic Person Test	2.9	0.39	2.5	1.8	2.7	1.1
Element Collection Test	2.3	0.23	1.5	1.4	1.9	0.83
Inheritance Test	2.9	0.42	3.5	2.6	3.2	1.5
Indexing Test	3.0	0.46	4.2	3.1	3.6	1.8
Graph (Binary Tree) Test	1.2	0.67	0.58	0.41	0.91	0.54
Multithreading Test	6.8	0.48	2.5	2.6	4.6	1.5
All Tests	3.2	0.44	2.5	2.0	2.8	1.2

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

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (0.48) to the normalized speed of Hibernate with Derby database server (6.8) reveals that in that case, Hibernate with Derby server is 14.2 times faster than EclipseLink with MySQL 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 MySQL server	Hibernate Derby server	EclipseLink MySQL server	Hibernate Derby server	EclipseLink MySQL server
Basic Person Test	2.9	0.35	3.5	1.7	3.2	1.0
Element Collection Test	1.7	0.11	0.87	0.51	1.3	0.31
Inheritance Test	2.9	0.29	3.6	1.6	3.2	0.94
Indexing Test	3.7	0.46	3.6	1.9	3.7	1.2
Graph (Binary Tree) Test	0.69	0.54	0.70	0.49	0.70	0.51
Multithreading Test	6.2	0.31	5.1	3.6	5.6	1.9
All Tests	3.0	0.34	2.9	1.6	3.0	0.98

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

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (0.31) to the normalized speed of Hibernate with Derby database server (6.2) reveals that in that case, Hibernate with Derby server is 20.0 times faster than EclipseLink with MySQL 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 MySQL server	Hibernate Derby server	EclipseLink MySQL server	Hibernate Derby server	EclipseLink MySQL server
Basic Person Test	9.5	1.3	4.3	4.2	6.9	2.7
Element Collection Test	8.2	0.69	1.1	0.89	4.6	0.79
Inheritance Test	6.6	1.1	5.0	4.8	5.8	2.9
Indexing Test	3.3	1.4	6.1	4.9	4.7	3.2
Graph (Binary Tree) Test	1.2	0.85	1.0	0.73	1.1	0.79
Multithreading Test	12.8	2.0	6.0	4.0	9.4	3.0
All Tests	7.1	1.2	4.0	3.3	5.6	2.3

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

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.69) to the normalized speed of Hibernate with Derby database server (8.2) reveals that in that case, Hibernate with Derby server is 11.9 times faster than EclipseLink with MySQL server.

JPA Performance Benchmark (JPAB)