Comparison of EclipseLink with H2 server vs OpenJPA 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
	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server
Basic Person Test	5.6	3.9	2.5	1.6	4.0	2.7
Element Collection Test	4.2	1.6	1.5	0.68	2.8	1.1
Inheritance Test	6.6	3.6	2.1	1.4	4.4	2.5
Indexing Test	9.7	5.6	4.1	2.4	6.9	4.0
Graph (Binary Tree) Test	4.7	0.68	3.5	0.57	4.1	0.63
Multithreading Test	10.2	7.2	4.0	2.7	7.1	4.9
All Tests	6.8	3.7	2.9	1.5	4.9	2.6

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

A large performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of OpenJPA with MySQL database server (0.68) to the normalized speed of EclipseLink with H2 database server (4.7) reveals that in that case, EclipseLink with H2 server is 6.9 times faster than OpenJPA with MySQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server
Basic Person Test	5.5	3.2	8.2	22.7	6.8	12.9
Element Collection Test	3.2	0.0038	4.2	2.9	3.7	1.4
Inheritance Test	4.7	0.017	10.1	6.9	7.4	3.4
Indexing Test	4.4	2.4	9.4	23.4	6.9	12.9
Graph (Binary Tree) Test	1.1	0.27	1.9	0.35	1.5	0.31
Multithreading Test	12.2	0.14	15.9	18.1	14.0	9.1
All Tests	5.2	1.0	8.3	12.4	6.7	6.7

The results above show that in general EclipseLink with H2 server is equivalent to OpenJPA with MySQL server in retrieving JPA entity objects from the database.

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with MySQL database server (0.0038) to the normalized speed of EclipseLink with H2 database server (3.2) reveals that in that case, EclipseLink with H2 server is 842 times faster than OpenJPA with MySQL server.

On the other hand, EclipseLink with H2 server is slower, for instance, when using simple basic entities with large retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (8.2) to the normalized speed of OpenJPA with MySQL database server (22.7) reveals that in that case, EclipseLink with H2 server is 2.8 times slower than OpenJPA with MySQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server
Basic Person Test	3.8	9.3	1.1	2.2	2.5	5.8
Element Collection Test	4.1	4.8	1.1	1.1	2.6	2.9
Inheritance Test	3.2	1.5	1.3	0.90	2.3	1.2
Indexing Test	3.0	0.31	8.0	2.1	5.5	1.2
Multithreading Test	1.1	1.9	1.0	0.99	1.1	1.4
All Tests	3.0	3.6	2.5	1.5	2.8	2.5

The results above show that in general EclipseLink with H2 server is slightly more efficient than OpenJPA with MySQL server in executing the tested JPA queries.

A large performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of OpenJPA with MySQL database server (0.31) to the normalized speed of EclipseLink with H2 database server (3.0) reveals that in that case, EclipseLink with H2 server is 9.7 times faster than OpenJPA with MySQL server.

On the other hand, EclipseLink with H2 server is slower, for instance, when using simple basic entities with small retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (3.8) to the normalized speed of OpenJPA with MySQL database server (9.3) reveals that in that case, EclipseLink with H2 server is 2.4 times slower than OpenJPA with MySQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server
Basic Person Test	4.5	0.74	2.2	1.6	3.4	1.2
Element Collection Test	3.8	0.014	2.4	1.7	3.1	0.87
Inheritance Test	4.4	0.048	3.0	2.0	3.7	1.0
Indexing Test	4.2	0.74	3.1	3.0	3.7	1.9
Graph (Binary Tree) Test	1.4	0.45	0.79	0.25	1.1	0.35
Multithreading Test	7.8	0.55	2.5	2.9	5.1	1.7
All Tests	4.3	0.42	2.3	1.9	3.3	1.2

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with MySQL database server (0.014) to the normalized speed of EclipseLink with H2 database server (3.8) reveals that in that case, EclipseLink with H2 server is 271 times faster than OpenJPA with MySQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server
Basic Person Test	6.4	0.98	3.1	1.7	4.8	1.4
Element Collection Test	3.0	0.0099	1.3	0.65	2.2	0.33
Inheritance Test	5.6	0.033	2.8	1.5	4.2	0.75
Indexing Test	10.3	0.64	3.8	2.0	7.0	1.3
Graph (Binary Tree) Test	1.5	0.41	1.3	0.43	1.4	0.42
Multithreading Test	7.0	0.27	4.9	2.9	6.0	1.6
All Tests	5.6	0.39	2.9	1.5	4.3	0.96

The results above show that in general EclipseLink with H2 server is much more efficient than OpenJPA with MySQL server in deleting JPA entity objects from the database. Comparing the normalized speed of OpenJPA with MySQL database server (0.96) to the normalized speed of EclipseLink with H2 database server (4.3) reveals that in these tests, EclipseLink with H2 server is 4.5 times faster than OpenJPA with MySQL server.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with MySQL database server (0.0099) to the normalized speed of EclipseLink with H2 database server (3.0) reveals that in that case, EclipseLink with H2 server is 303 times faster than OpenJPA 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 H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server	EclipseLink H2 server	OpenJPA MySQL server
Basic Person Test	5.2	3.6	3.4	6.0	4.3	4.8
Element Collection Test	3.6	1.3	2.1	1.4	2.9	1.3
Inheritance Test	4.9	1.0	3.9	2.5	4.4	1.8
Indexing Test	6.3	1.9	5.7	6.6	6.0	4.3
Graph (Binary Tree) Test	2.1	0.45	1.9	0.40	2.0	0.43
Multithreading Test	7.7	2.0	5.7	5.5	6.7	3.8
All Tests	5.1	1.8	3.8	3.9	4.5	2.8

The results above show that in general EclipseLink with H2 server is more efficient than OpenJPA with MySQL server in performing JPA database operations.

A large performance gap has been detected when using class inheritance in the object model with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with MySQL database server (1.0) to the normalized speed of EclipseLink with H2 database server (4.9) reveals that in that case, EclipseLink with H2 server is 4.9 times faster than OpenJPA with MySQL server.

JPA Performance Benchmark (JPAB)