Comparison of EclipseLink with Derby server vs OpenJPA with PostgreSQL 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 PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server
Basic Person Test	3.8	5.2	3.1	4.8	3.4	5.0
Element Collection Test	2.2	2.8	1.5	2.2	1.8	2.5
Inheritance Test	3.9	4.6	2.9	3.2	3.4	3.9
Indexing Test	5.2	7.4	4.3	6.9	4.7	7.1
Graph (Binary Tree) Test	1.9	0.98	1.7	0.81	1.8	0.89
Multithreading Test	6.1	23.4	3.9	9.1	5.0	16.2
All Tests	3.8	7.4	2.9	4.5	3.4	5.9

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

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

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using graphs of objects with large transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.81) to the normalized speed of EclipseLink with Derby database server (1.7) reveals that in that case, OpenJPA with PostgreSQL server is 2.1 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 PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server
Basic Person Test	6.4	5.8	11.3	16.1	8.8	10.9
Element Collection Test	1.8	0.013	2.4	8.7	2.1	4.4
Inheritance Test	3.7	5.2	12.9	17.6	8.3	11.4
Indexing Test	3.6	4.8	12.8	18.7	8.2	11.8
Graph (Binary Tree) Test	0.61	0.27	0.73	0.35	0.67	0.31
Multithreading Test	8.5	11.9	19.8	23.3	14.1	17.6
All Tests	4.1	4.7	10.0	14.1	7.0	9.4

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

A large performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (2.4) to the normalized speed of OpenJPA with PostgreSQL database server (8.7) reveals that in that case, OpenJPA with PostgreSQL server is 3.6 times faster than EclipseLink with Derby server.

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.013) to the normalized speed of EclipseLink with Derby database server (1.8) reveals that in that case, OpenJPA with PostgreSQL server is 138 times slower than EclipseLink with Derby 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 PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server
Basic Person Test	45.8	failed	5.3	failed	25.6	failed
Element Collection Test	35.2	failed	0.99	failed	18.1	failed
Inheritance Test	23.1	failed	5.9	failed	14.5	failed
Indexing Test	2.5	failed	12.2	failed	7.4	failed
Multithreading Test	34.3	failed	7.7	failed	21.0	failed
All Tests	28.2	failed	6.4	failed	17.3	failed

OpenJPA with PostgreSQL server has failed in 10 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	OpenJPA PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server
Basic Person Test	3.9	4.9	4.4	3.9	4.1	4.4
Element Collection Test	1.7	0.033	1.6	4.6	1.6	2.3
Inheritance Test	4.6	4.8	6.1	4.9	5.3	4.9
Indexing Test	4.5	5.1	7.6	6.0	6.1	5.6
Graph (Binary Tree) Test	0.70	0.57	0.42	0.31	0.56	0.44
Multithreading Test	7.3	22.2	4.8	7.4	6.0	14.8
All Tests	3.8	6.3	4.2	4.5	4.0	5.4

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

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

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.033) to the normalized speed of EclipseLink with Derby database server (1.7) reveals that in that case, OpenJPA with PostgreSQL server is 51.5 times slower than EclipseLink with Derby 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 PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server
Basic Person Test	2.8	4.6	3.9	5.3	3.3	5.0
Element Collection Test	1.2	0.032	0.55	2.8	0.87	1.4
Inheritance Test	3.3	4.3	3.7	4.6	3.5	4.4
Indexing Test	4.9	8.0	3.5	7.1	4.2	7.5
Graph (Binary Tree) Test	0.51	0.53	0.50	0.55	0.51	0.54
Multithreading Test	4.8	17.4	5.7	9.1	5.3	13.3
All Tests	2.9	5.8	3.0	4.9	3.0	5.4

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

A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with Derby database server (0.55) to the normalized speed of OpenJPA with PostgreSQL database server (2.8) reveals that in that case, OpenJPA with PostgreSQL server is 5.1 times faster than EclipseLink with Derby server.

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.032) to the normalized speed of EclipseLink with Derby database server (1.2) reveals that in that case, OpenJPA with PostgreSQL server is 37.5 times slower than EclipseLink 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 Derby server	OpenJPA PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server	EclipseLink Derby server	OpenJPA PostgreSQL server
Basic Person Test	12.5	5.1	5.6	7.5	9.1	6.3
Element Collection Test	8.4	0.72	1.4	4.6	4.9	2.6
Inheritance Test	7.7	4.7	6.3	7.6	7.0	6.2
Indexing Test	4.1	6.3	8.1	9.7	6.1	8.0
Graph (Binary Tree) Test	0.93	0.59	0.83	0.50	0.88	0.55
Multithreading Test	12.2	18.7	8.4	12.2	10.3	15.5
All Tests	7.9	6.0	5.2	7.0	6.6	6.5

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

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

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

JPA Performance Benchmark (JPAB)