Comparison of EclipseLink with PostgreSQL server vs OpenJPA with Derby 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 PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server
Basic Person Test	7.3	3.1	4.2	2.7	5.8	2.9
Element Collection Test	3.1	2.0	1.9	1.7	2.5	1.8
Inheritance Test	6.9	3.0	5.0	2.3	5.9	2.6
Indexing Test	10.0	4.7	6.8	4.1	8.4	4.4
Graph (Binary Tree) Test	3.5	0.71	3.3	0.64	3.4	0.67
Multithreading Test	31.8	6.0	14.5	3.8	23.1	4.9
All Tests	10.4	3.3	6.0	2.5	8.2	2.9

The results above show that in general EclipseLink with PostgreSQL server is more efficient than OpenJPA with Derby server in persisting JPA entity objects to the database. Comparing the normalized speed of OpenJPA with Derby database server (2.9) to the normalized speed of EclipseLink with PostgreSQL database server (8.2) reveals that in these tests, EclipseLink with PostgreSQL server is 2.8 times faster than OpenJPA with Derby server.

A large performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (6.0) to the normalized speed of EclipseLink with PostgreSQL database server (31.8) reveals that in that case, EclipseLink with PostgreSQL server is 5.3 times faster than OpenJPA with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server
Basic Person Test	6.8	0.78	17.2	11.6	12.0	6.2
Element Collection Test	0.026	0.0024	0.020	1.1	0.023	0.54
Inheritance Test	6.0	0.014	19.7	5.0	12.9	2.5
Indexing Test	5.6	0.62	19.5	13.0	12.6	6.8
Graph (Binary Tree) Test	0.47	0.065	0.61	0.39	0.54	0.23
Multithreading Test	13.5	1.6	27.8	19.0	20.6	10.3
All Tests	5.4	0.51	14.1	8.4	9.8	4.4

The results above show that in general EclipseLink with PostgreSQL server is more efficient than OpenJPA with Derby server in retrieving JPA entity objects from the database. Comparing the normalized speed of OpenJPA with Derby database server (4.4) to the normalized speed of EclipseLink with PostgreSQL database server (9.8) reveals that in these tests, EclipseLink with PostgreSQL server is 2.2 times faster than OpenJPA with Derby server.

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of OpenJPA with Derby database server (0.014) to the normalized speed of EclipseLink with PostgreSQL database server (6.0) reveals that in that case, EclipseLink with PostgreSQL server is 429 times faster than OpenJPA with Derby server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.020) to the normalized speed of OpenJPA with Derby database server (1.1) reveals that in that case, EclipseLink with PostgreSQL server is 55.0 times slower than OpenJPA with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server
Basic Person Test	55.5	29.2	7.8	5.5	31.6	17.3
Element Collection Test	15.4	2.2	0.028	1.4	7.7	1.8
Inheritance Test	54.9	2.2	11.5	1.0	33.2	1.6
Indexing Test	0.077	2.2	10.0	11.7	5.1	7.0
Multithreading Test	55.3	35.5	12.0	8.3	33.7	21.9
All Tests	36.2	14.3	8.3	5.6	22.3	9.9

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

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of OpenJPA with Derby database server (2.2) to the normalized speed of EclipseLink with PostgreSQL database server (54.9) reveals that in that case, EclipseLink with PostgreSQL server is 25.0 times faster than OpenJPA with Derby server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.028) to the normalized speed of OpenJPA with Derby database server (1.4) reveals that in that case, EclipseLink with PostgreSQL server is 50.0 times slower than OpenJPA with Derby server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server
Basic Person Test	6.2	1.5	4.1	4.0	5.1	2.8
Element Collection Test	0.080	0.0081	0.028	1.9	0.054	0.94
Inheritance Test	6.4	0.043	6.1	3.8	6.2	1.9
Indexing Test	6.5	1.8	7.0	6.8	6.8	4.3
Graph (Binary Tree) Test	0.90	0.16	0.50	0.27	0.70	0.22
Multithreading Test	36.0	6.9	9.1	5.0	22.5	5.9
All Tests	9.3	1.7	4.5	3.6	6.9	2.7

The results above show that in general EclipseLink with PostgreSQL server is more efficient than OpenJPA with Derby server in updating JPA entity objects in the database. Comparing the normalized speed of OpenJPA with Derby database server (2.7) to the normalized speed of EclipseLink with PostgreSQL database server (6.9) reveals that in these tests, EclipseLink with PostgreSQL server is 2.6 times faster than OpenJPA with Derby server.

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (0.043) to the normalized speed of EclipseLink with PostgreSQL database server (6.4) reveals that in that case, EclipseLink with PostgreSQL server is 149 times faster than OpenJPA with Derby server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.028) to the normalized speed of OpenJPA with Derby database server (1.9) reveals that in that case, EclipseLink with PostgreSQL server is 67.9 times slower than OpenJPA with Derby server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server
Basic Person Test	5.7	1.4	5.7	3.7	5.7	2.5
Element Collection Test	0.025	0.0082	stopped	1.4	0.012	0.71
Inheritance Test	5.5	0.035	5.4	2.5	5.4	1.3
Indexing Test	10.4	2.3	10.0	3.5	10.2	2.9
Graph (Binary Tree) Test	0.016	0.13	0.013	0.35	0.015	0.24
Multithreading Test	26.3	3.6	16.8	4.0	21.6	3.8
All Tests	8.0	1.3	6.3	2.6	7.2	1.9

The results above show that in general EclipseLink with PostgreSQL server is much more efficient than OpenJPA with Derby server in deleting JPA entity objects from the database. Comparing the normalized speed of OpenJPA with Derby database server (1.9) to the normalized speed of EclipseLink with PostgreSQL database server (7.2) reveals that in these tests, EclipseLink with PostgreSQL server is 3.8 times faster than OpenJPA with Derby server.

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (0.035) to the normalized speed of EclipseLink with PostgreSQL database server (5.5) reveals that in that case, EclipseLink with PostgreSQL server is 157 times faster than OpenJPA with Derby server.

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

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server	EclipseLink PostgreSQL server	OpenJPA Derby server
Basic Person Test	16.3	7.2	7.8	5.5	12.1	6.4
Element Collection Test	3.7	0.84	0.40	1.5	2.1	1.2
Inheritance Test	15.9	1.1	9.5	2.9	12.7	2.0
Indexing Test	6.5	2.3	10.7	7.8	8.6	5.1
Graph (Binary Tree) Test	1.2	0.27	1.1	0.41	1.2	0.34
Multithreading Test	32.6	10.7	16.0	8.0	24.3	9.4
All Tests	13.1	3.9	7.8	4.5	10.5	4.2

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

A huge 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 Derby database server (1.1) to the normalized speed of EclipseLink with PostgreSQL database server (15.9) reveals that in that case, EclipseLink with PostgreSQL server is 14.5 times faster than OpenJPA with Derby server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.40) to the normalized speed of OpenJPA with Derby database server (1.5) reveals that in that case, EclipseLink with PostgreSQL server is 3.8 times slower than OpenJPA with Derby server.

JPA Performance Benchmark (JPAB)