• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with MySQL server vs Hibernate 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
	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded
Basic Person Test	3.6	0.083	1.5	1.0	2.6	0.55
Element Collection Test	1.5	0.067	0.69	0.69	1.1	0.38
Inheritance Test	3.5	0.080	1.4	0.99	2.4	0.54
Indexing Test	5.3	0.098	2.5	1.0	3.9	0.55
Graph (Binary Tree) Test	1.7	0.27	1.3	0.96	1.5	0.61
Multithreading Test	7.2	failed	2.4	failed	4.8	failed
All Tests	3.8	0.12	1.6	0.93	2.7	0.53

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

The results above show that in general EclipseLink with MySQL server 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 MySQL database server (2.7) reveals that in these tests, EclipseLink with MySQL server is 5.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 MySQL database server (5.3) reveals that in that case, EclipseLink with MySQL server is 54.1 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
	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded
Basic Person Test	0.43	1.8	15.5	1.3	8.0	1.5
Element Collection Test	0.16	0.0008	1.4	failed	0.78	0.0008
Inheritance Test	0.39	2.4	17.6	1.4	9.0	1.9
Indexing Test	0.43	1.9	16.6	2.3	8.5	2.1
Graph (Binary Tree) Test	0.53	0.56	0.76	0.88	0.65	0.72
Multithreading Test	0.19	failed	11.0	failed	5.6	failed
All Tests	0.35	1.3	10.5	1.5	5.4	1.4

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

The results above show that in general EclipseLink with MySQL server 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 MySQL database server (5.4) reveals that in these tests, EclipseLink with MySQL server is 3.9 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 MySQL database server (0.16) reveals that in that case, EclipseLink with MySQL server is 200 times faster than Hibernate with SQLite embedded.

On the other hand, EclipseLink with MySQL server is slower, for instance, when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.39) to the normalized speed of Hibernate with SQLite embedded database (2.4) reveals that in that case, EclipseLink with MySQL server is 6.2 times slower 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
	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded
Basic Person Test	1.5	1.1	0.44	0.22	0.95	0.65
Element Collection Test	1.4	0.39	0.43	failed	0.92	0.39
Inheritance Test	1.1	0.53	0.61	0.28	0.86	0.40
Indexing Test	0.26	0.0011	0.52	0.43	0.39	0.21
Multithreading Test	1.9	failed	0.72	failed	1.3	failed
All Tests	1.2	0.50	0.54	0.31	0.88	0.42

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

The results above show that in general EclipseLink with MySQL server is 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 MySQL database server (0.88) reveals that in these tests, EclipseLink with MySQL server is 2.1 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 MySQL database server (0.26) reveals that in that case, EclipseLink with MySQL server is 236 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
	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded
Basic Person Test	0.39	0.076	1.8	0.65	1.1	0.37
Element Collection Test	0.23	0.0022	1.4	failed	0.83	0.0022
Inheritance Test	0.42	0.079	2.6	0.97	1.5	0.53
Indexing Test	0.46	0.057	3.1	0.54	1.8	0.30
Graph (Binary Tree) Test	0.67	0.26	0.41	0.42	0.54	0.34
Multithreading Test	0.48	failed	2.6	failed	1.5	failed
All Tests	0.44	0.094	2.0	0.65	1.2	0.34

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

The results above show that in general EclipseLink with MySQL server 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 MySQL database server (1.2) reveals that in these tests, EclipseLink with MySQL server is 3.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.0022) to the normalized speed of EclipseLink with MySQL database server (0.23) reveals that in that case, EclipseLink with MySQL server is 105 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
	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded
Basic Person Test	0.35	0.061	1.7	0.91	1.0	0.49
Element Collection Test	0.11	0.0007	0.51	failed	0.31	0.0007
Inheritance Test	0.29	0.058	1.6	0.90	0.94	0.48
Indexing Test	0.46	0.079	1.9	0.54	1.2	0.31
Graph (Binary Tree) Test	0.54	0.24	0.49	0.80	0.51	0.52
Multithreading Test	0.31	failed	3.6	failed	1.9	failed
All Tests	0.34	0.088	1.6	0.79	0.98	0.40

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

The results above show that in general EclipseLink with MySQL server is 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 MySQL database server (0.98) reveals that in these tests, EclipseLink with MySQL server is 2.4 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 MySQL database server (0.11) reveals that in that case, EclipseLink with MySQL server is 157 times faster than Hibernate with SQLite embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded	EclipseLink MySQL server	Hibernate SQLite embedded
Basic Person Test	1.3	0.63	4.2	0.81	2.7	0.72
Element Collection Test	0.69	0.092	0.89	0.69	0.79	0.19
Inheritance Test	1.1	0.63	4.8	0.91	2.9	0.77
Indexing Test	1.4	0.42	4.9	0.96	3.2	0.69
Graph (Binary Tree) Test	0.85	0.33	0.73	0.77	0.79	0.55
Multithreading Test	2.0	failed	4.0	failed	3.0	failed
All Tests	1.2	0.42	3.3	0.86	2.3	0.62

The results above show that in general EclipseLink with MySQL server 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 MySQL database server (2.3) reveals that in these tests, EclipseLink with MySQL server is 3.7 times faster than Hibernate with SQLite embedded.

A large 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 MySQL database server (0.69) reveals that in that case, EclipseLink with MySQL server is 7.5 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.