Comparison of EclipseLink with Derby server vs OpenJPA with H2 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 Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server
Basic Person Test	3.8	3.7	3.1	2.2	3.4	2.9
Element Collection Test	2.2	2.6	1.5	1.5	1.8	2.1
Inheritance Test	3.9	4.5	2.9	2.0	3.4	3.2
Indexing Test	5.2	7.3	4.3	3.6	4.7	5.4
Graph (Binary Tree) Test	1.9	1.1	1.7	0.84	1.8	0.97
Multithreading Test	6.1	7.7	3.9	4.2	5.0	5.9
All Tests	3.8	4.5	2.9	2.4	3.4	3.4

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

On the other hand, OpenJPA with H2 server is slower, for instance, when using graphs of objects with large transaction size. Comparing the normalized speed of OpenJPA with H2 database server (0.84) to the normalized speed of EclipseLink with Derby database server (1.7) reveals that in that case, OpenJPA with H2 server is 2.0 times slower than EclipseLink with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server
Basic Person Test	6.4	2.9	11.3	7.6	8.8	5.2
Element Collection Test	1.8	0.0022	2.4	1.9	2.1	0.93
Inheritance Test	3.7	0.013	12.9	4.0	8.3	2.0
Indexing Test	3.6	4.1	12.8	8.8	8.2	6.5
Graph (Binary Tree) Test	0.61	0.38	0.73	0.49	0.67	0.44
Multithreading Test	8.5	5.9	19.8	14.0	14.1	10.0
All Tests	4.1	2.2	10.0	6.1	7.0	4.2

The results above show that in general EclipseLink with Derby server is more efficient than OpenJPA with H2 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 H2 database server (0.0022) to the normalized speed of EclipseLink with Derby database server (1.8) reveals that in that case, EclipseLink with Derby server is 818 times faster than OpenJPA with H2 server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server
Basic Person Test	45.8	3.7	5.3	1.0	25.6	2.4
Element Collection Test	35.2	2.0	0.99	1.2	18.1	1.6
Inheritance Test	23.1	2.8	5.9	1.1	14.5	2.0
Indexing Test	2.5	3.8	12.2	7.5	7.4	5.7
Multithreading Test	34.3	0.98	7.7	1.0	21.0	1.0
All Tests	28.2	2.7	6.4	2.4	17.3	2.5

The results above show that in general EclipseLink with Derby server is much more efficient than OpenJPA with H2 server in executing the tested JPA queries. Comparing the normalized speed of OpenJPA with H2 database server (2.5) to the normalized speed of EclipseLink with Derby database server (17.3) reveals that in these tests, EclipseLink with Derby server is 6.9 times faster than OpenJPA with H2 server.

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server
Basic Person Test	3.9	3.0	4.4	2.0	4.1	2.5
Element Collection Test	1.7	0.0078	1.6	1.9	1.6	0.94
Inheritance Test	4.6	0.034	6.1	2.8	5.3	1.4
Indexing Test	4.5	2.8	7.6	3.2	6.1	3.0
Graph (Binary Tree) Test	0.70	0.79	0.42	0.43	0.56	0.61
Multithreading Test	7.3	7.0	4.8	2.5	6.0	4.8
All Tests	3.8	2.3	4.2	2.1	4.0	2.2

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server
Basic Person Test	2.8	3.2	3.9	2.2	3.3	2.7
Element Collection Test	1.2	0.0060	0.55	0.88	0.87	0.44
Inheritance Test	3.3	0.030	3.7	3.1	3.5	1.6
Indexing Test	4.9	6.5	3.5	3.6	4.2	5.1
Graph (Binary Tree) Test	0.51	0.73	0.50	0.75	0.51	0.74
Multithreading Test	4.8	7.6	5.7	5.2	5.3	6.4
All Tests	2.9	3.0	3.0	2.6	3.0	2.8

The results above show that in general EclipseLink with Derby server is slightly more efficient than OpenJPA with H2 server in deleting JPA entity objects from the database.

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

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server	EclipseLink Derby server	OpenJPA H2 server
Basic Person Test	12.5	3.3	5.6	3.0	9.1	3.1
Element Collection Test	8.4	0.93	1.4	1.5	4.9	1.2
Inheritance Test	7.7	1.5	6.3	2.6	7.0	2.0
Indexing Test	4.1	4.9	8.1	5.4	6.1	5.1
Graph (Binary Tree) Test	0.93	0.75	0.83	0.63	0.88	0.69
Multithreading Test	12.2	5.9	8.4	5.4	10.3	5.6
All Tests	7.9	2.9	5.2	3.2	6.6	3.0

The results above show that in general EclipseLink with Derby server is more efficient than OpenJPA with H2 server in performing JPA database operations. Comparing the normalized speed of OpenJPA with H2 database server (3.0) to the normalized speed of EclipseLink with Derby database server (6.6) reveals that in these tests, EclipseLink with Derby server is 2.2 times faster than OpenJPA with H2 server.

A large performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with H2 database server (0.93) to the normalized speed of EclipseLink with Derby database server (8.4) reveals that in that case, EclipseLink with Derby server is 9.0 times faster than OpenJPA with H2 server.

JPA Performance Benchmark (JPAB)