Comparison of EclipseLink with MySQL server vs OpenJPA 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
	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded
Basic Person Test	3.6	17.1	1.5	5.8	2.6	11.5
Element Collection Test	1.5	10.9	0.69	4.9	1.1	7.9
Inheritance Test	3.5	14.3	1.4	5.9	2.4	10.1
Indexing Test	5.3	24.4	2.5	13.7	3.9	19.1
Graph (Binary Tree) Test	1.7	6.8	1.3	6.7	1.5	6.7
Multithreading Test	7.2	34.2	2.4	10.2	4.8	22.2
All Tests	3.8	17.9	1.6	7.9	2.7	12.9

The results above show that in general OpenJPA with H2 embedded is much more efficient than EclipseLink with MySQL server in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with MySQL database server (2.7) to the normalized speed of OpenJPA with H2 embedded database (12.9) reveals that in these tests, OpenJPA with H2 embedded is 4.8 times faster than EclipseLink with MySQL server.

A large performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (1.5) to the normalized speed of OpenJPA with H2 embedded database (10.9) reveals that in that case, OpenJPA with H2 embedded is 7.3 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
	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded
Basic Person Test	0.43	14.6	15.5	27.2	8.0	20.9
Element Collection Test	0.16	0.0046	1.4	4.3	0.78	2.1
Inheritance Test	0.39	0.011	17.6	7.4	9.0	3.7
Indexing Test	0.43	17.0	16.6	35.0	8.5	26.0
Graph (Binary Tree) Test	0.53	1.0	0.76	1.4	0.65	1.2
Multithreading Test	0.19	18.7	11.0	27.6	5.6	23.1
All Tests	0.35	8.6	10.5	17.1	5.4	12.8

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

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

On the other hand, OpenJPA with H2 embedded is slower, for instance, when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of OpenJPA with H2 embedded database (0.011) to the normalized speed of EclipseLink with MySQL database server (0.39) reveals that in that case, OpenJPA with H2 embedded is 35.5 times slower than EclipseLink with MySQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded
Basic Person Test	1.5	5.0	0.44	1.1	0.95	3.1
Element Collection Test	1.4	1.7	0.43	1.3	0.92	1.5
Inheritance Test	1.1	2.2	0.61	1.2	0.86	1.7
Indexing Test	0.26	13.8	0.52	23.2	0.39	18.5
Multithreading Test	1.9	1.4	0.72	0.60	1.3	0.99
All Tests	1.2	4.8	0.54	5.5	0.88	5.1

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

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.26) to the normalized speed of OpenJPA with H2 embedded database (13.8) reveals that in that case, OpenJPA with H2 embedded is 53.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
	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded
Basic Person Test	0.39	10.0	1.8	6.0	1.1	8.0
Element Collection Test	0.23	0.011	1.4	3.8	0.83	1.9
Inheritance Test	0.42	0.046	2.6	5.0	1.5	2.5
Indexing Test	0.46	8.9	3.1	7.0	1.8	8.0
Graph (Binary Tree) Test	0.67	2.4	0.41	1.3	0.54	1.9
Multithreading Test	0.48	16.6	2.6	4.3	1.5	10.4
All Tests	0.44	6.3	2.0	4.6	1.2	5.4

The results above show that in general OpenJPA with H2 embedded is much 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 OpenJPA with H2 embedded database (5.4) reveals that in these tests, OpenJPA with H2 embedded is 4.5 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 OpenJPA with H2 embedded database (16.6) reveals that in that case, OpenJPA with H2 embedded is 34.6 times faster than EclipseLink with MySQL server.

On the other hand, OpenJPA with H2 embedded is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with H2 embedded database (0.011) to the normalized speed of EclipseLink with MySQL database server (0.23) reveals that in that case, OpenJPA with H2 embedded is 20.9 times slower 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
	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded
Basic Person Test	0.35	18.3	1.7	11.1	1.0	14.7
Element Collection Test	0.11	0.012	0.51	2.9	0.31	1.4
Inheritance Test	0.29	0.030	1.6	6.6	0.94	3.3
Indexing Test	0.46	23.2	1.9	9.7	1.2	16.4
Graph (Binary Tree) Test	0.54	1.8	0.49	2.4	0.51	2.1
Multithreading Test	0.31	31.2	3.6	17.3	1.9	24.2
All Tests	0.34	12.4	1.6	8.3	0.98	10.4

The results above show that in general OpenJPA with H2 embedded 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 OpenJPA with H2 embedded database (10.4) reveals that in these tests, OpenJPA with H2 embedded is 10.6 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 OpenJPA with H2 embedded database (31.2) reveals that in that case, OpenJPA with H2 embedded is 101 times faster than EclipseLink with MySQL server.

On the other hand, OpenJPA with H2 embedded is slower, for instance, when using class inheritance in the object model with small transaction size. Comparing the normalized speed of OpenJPA with H2 embedded database (0.030) to the normalized speed of EclipseLink with MySQL database server (0.29) reveals that in that case, OpenJPA with H2 embedded is 9.7 times slower 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
	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded	EclipseLink MySQL server	OpenJPA H2 embedded
Basic Person Test	1.3	13.0	4.2	10.2	2.7	11.6
Element Collection Test	0.69	2.5	0.89	3.4	0.79	3.0
Inheritance Test	1.1	3.3	4.8	5.2	2.9	4.3
Indexing Test	1.4	17.5	4.9	17.7	3.2	17.6
Graph (Binary Tree) Test	0.85	3.0	0.73	3.0	0.79	3.0
Multithreading Test	2.0	20.4	4.0	12.0	3.0	16.2
All Tests	1.2	10.2	3.3	8.8	2.3	9.5

The results above show that in general OpenJPA with H2 embedded is much 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 OpenJPA with H2 embedded database (9.5) reveals that in these tests, OpenJPA with H2 embedded is 4.1 times faster than EclipseLink with MySQL server.

A huge performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (1.4) to the normalized speed of OpenJPA with H2 embedded database (17.5) reveals that in that case, OpenJPA with H2 embedded is 12.5 times faster than EclipseLink with MySQL server.

JPA Performance Benchmark (JPAB)