Comparison of EclipseLink with MySQL server vs OpenJPA with HSQLDB 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 HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded
Basic Person Test	3.6	13.3	1.5	6.9	2.6	10.1
Element Collection Test	1.5	8.6	0.69	5.3	1.1	7.0
Inheritance Test	3.5	12.2	1.4	5.8	2.4	9.0
Indexing Test	5.3	16.7	2.5	9.1	3.9	12.9
Graph (Binary Tree) Test	1.7	6.1	1.3	7.3	1.5	6.7
Multithreading Test	7.2	26.8	2.4	7.0	4.8	16.9
All Tests	3.8	13.9	1.6	6.9	2.7	10.4

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

A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (0.69) to the normalized speed of OpenJPA with HSQLDB embedded database (5.3) reveals that in that case, OpenJPA with HSQLDB embedded is 7.7 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 HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded
Basic Person Test	0.43	21.8	15.5	30.1	8.0	25.9
Element Collection Test	0.16	0.0068	1.4	4.5	0.78	2.2
Inheritance Test	0.39	0.0025	17.6	2.0	9.0	0.98
Indexing Test	0.43	22.1	16.6	43.6	8.5	32.9
Graph (Binary Tree) Test	0.53	2.1	0.76	2.1	0.65	2.1
Multithreading Test	0.19	20.9	11.0	23.5	5.6	22.2
All Tests	0.35	11.1	10.5	17.6	5.4	14.4

The results above show that in general OpenJPA with HSQLDB 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 HSQLDB embedded database (14.4) reveals that in these tests, OpenJPA with HSQLDB embedded is 2.7 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 HSQLDB embedded database (20.9) reveals that in that case, OpenJPA with HSQLDB embedded is 110 times faster than EclipseLink with MySQL server.

On the other hand, OpenJPA with HSQLDB embedded is slower, for instance, when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of OpenJPA with HSQLDB embedded database (0.0025) to the normalized speed of EclipseLink with MySQL database server (0.39) reveals that in that case, OpenJPA with HSQLDB embedded is 156 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 HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded
Basic Person Test	1.5	2.8	0.44	0.91	0.95	1.9
Element Collection Test	1.4	1.4	0.43	0.95	0.92	1.2
Inheritance Test	1.1	2.4	0.61	1.3	0.86	1.8
Indexing Test	0.26	15.4	0.52	34.3	0.39	24.9
Multithreading Test	1.9	1.4	0.72	0.53	1.3	0.95
All Tests	1.2	4.7	0.54	7.6	0.88	6.1

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

A huge performance gap has been detected when using database indexes with large retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.52) to the normalized speed of OpenJPA with HSQLDB embedded database (34.3) reveals that in that case, OpenJPA with HSQLDB embedded is 66.0 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 HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded
Basic Person Test	0.39	12.0	1.8	5.3	1.1	8.6
Element Collection Test	0.23	0.017	1.4	3.7	0.83	1.8
Inheritance Test	0.42	0.0098	2.6	2.0	1.5	0.99
Indexing Test	0.46	9.3	3.1	5.5	1.8	7.4
Graph (Binary Tree) Test	0.67	2.5	0.41	1.6	0.54	2.1
Multithreading Test	0.48	20.0	2.6	3.7	1.5	11.8
All Tests	0.44	7.3	2.0	3.6	1.2	5.5

The results above show that in general OpenJPA with HSQLDB 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 HSQLDB embedded database (5.5) reveals that in these tests, OpenJPA with HSQLDB embedded is 4.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.48) to the normalized speed of OpenJPA with HSQLDB embedded database (20.0) reveals that in that case, OpenJPA with HSQLDB embedded is 41.7 times faster than EclipseLink with MySQL server.

On the other hand, OpenJPA with HSQLDB embedded is slower, for instance, when using class inheritance in the object model with small transaction size. Comparing the normalized speed of OpenJPA with HSQLDB embedded database (0.0098) to the normalized speed of EclipseLink with MySQL database server (0.42) reveals that in that case, OpenJPA with HSQLDB embedded is 42.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 HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded
Basic Person Test	0.35	21.3	1.7	15.7	1.0	18.5
Element Collection Test	0.11	0.011	0.51	2.9	0.31	1.5
Inheritance Test	0.29	0.0070	1.6	3.5	0.94	1.8
Indexing Test	0.46	28.8	1.9	15.2	1.2	22.0
Graph (Binary Tree) Test	0.54	2.9	0.49	3.6	0.51	3.2
Multithreading Test	0.31	26.0	3.6	19.6	1.9	22.8
All Tests	0.34	13.2	1.6	10.1	0.98	11.6

The results above show that in general OpenJPA with HSQLDB 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 HSQLDB embedded database (11.6) reveals that in these tests, OpenJPA with HSQLDB embedded is 11.8 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 HSQLDB embedded database (26.0) reveals that in that case, OpenJPA with HSQLDB embedded is 83.9 times faster than EclipseLink with MySQL server.

On the other hand, OpenJPA with HSQLDB embedded is slower, for instance, when using class inheritance in the object model with small transaction size. Comparing the normalized speed of OpenJPA with HSQLDB embedded database (0.0070) to the normalized speed of EclipseLink with MySQL database server (0.29) reveals that in that case, OpenJPA with HSQLDB embedded is 41.4 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 HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded	EclipseLink MySQL server	OpenJPA HSQLDB embedded
Basic Person Test	1.3	14.3	4.2	11.8	2.7	13.0
Element Collection Test	0.69	2.0	0.89	3.5	0.79	2.7
Inheritance Test	1.1	2.9	4.8	2.9	2.9	2.9
Indexing Test	1.4	18.5	4.9	21.6	3.2	20.0
Graph (Binary Tree) Test	0.85	3.4	0.73	3.7	0.79	3.5
Multithreading Test	2.0	19.0	4.0	10.9	3.0	14.9
All Tests	1.2	10.2	3.3	9.2	2.3	9.7

The results above show that in general OpenJPA with HSQLDB 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 HSQLDB embedded database (9.7) reveals that in these tests, OpenJPA with HSQLDB embedded is 4.2 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 HSQLDB embedded database (18.5) reveals that in that case, OpenJPA with HSQLDB embedded is 13.2 times faster than EclipseLink with MySQL server.

JPA Performance Benchmark (JPAB)