Comparison of OpenJPA with PostgreSQL server vs EclipseLink with Derby 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
	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	5.2	5.5	4.8	3.7	5.0	4.6
Element Collection Test	2.8	3.0	2.2	1.7	2.5	2.4
Inheritance Test	4.6	5.3	3.2	3.5	3.9	4.4
Indexing Test	7.4	6.9	6.9	4.6	7.1	5.8
Graph (Binary Tree) Test	0.98	2.0	0.81	1.9	0.89	1.9
Multithreading Test	23.4	9.3	9.1	4.1	16.2	6.7
All Tests	7.4	5.3	4.5	3.2	5.9	4.3

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

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 embedded database (1.9) reveals that in that case, OpenJPA with PostgreSQL server is 2.3 times slower than EclipseLink with Derby embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	5.8	16.4	16.1	58.7	10.9	37.5
Element Collection Test	0.013	7.5	8.7	13.3	4.4	10.4
Inheritance Test	5.2	17.1	17.6	58.9	11.4	38.0
Indexing Test	4.8	14.2	18.7	67.4	11.8	40.8
Graph (Binary Tree) Test	0.27	2.8	0.35	5.7	0.31	4.2
Multithreading Test	11.9	28.0	23.3	48.7	17.6	38.4
All Tests	4.7	14.3	14.1	42.1	9.4	28.2

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

A huge performance gap has been detected 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 embedded database (7.5) reveals that in that case, EclipseLink with Derby embedded is 577 times faster than OpenJPA with PostgreSQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	failed	53.4	failed	13.8	failed	33.6
Element Collection Test	failed	37.9	failed	4.4	failed	21.2
Inheritance Test	failed	37.4	failed	15.0	failed	26.2
Indexing Test	failed	7.6	failed	49.3	failed	28.4
Multithreading Test	failed	41.2	failed	6.1	failed	23.6
All Tests	failed	35.5	failed	17.7	failed	26.6

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
	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	4.9	6.4	3.9	6.7	4.4	6.5
Element Collection Test	0.033	5.4	4.6	6.2	2.3	5.8
Inheritance Test	4.8	6.5	4.9	9.2	4.9	7.8
Indexing Test	5.1	7.3	6.0	11.1	5.6	9.2
Graph (Binary Tree) Test	0.57	2.8	0.31	1.7	0.44	2.2
Multithreading Test	22.2	21.3	7.4	5.0	14.8	13.1
All Tests	6.3	8.3	4.5	6.6	5.4	7.5

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	4.6	4.6	5.3	4.7	5.0	4.6
Element Collection Test	0.032	2.5	2.8	1.4	1.4	1.9
Inheritance Test	4.3	3.9	4.6	4.5	4.4	4.2
Indexing Test	8.0	6.2	7.1	3.8	7.5	5.0
Graph (Binary Tree) Test	0.53	1.1	0.55	1.0	0.54	1.1
Multithreading Test	17.4	6.2	9.1	5.8	13.3	6.0
All Tests	5.8	4.1	4.9	3.5	5.4	3.8

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

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

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 embedded database (2.5) reveals that in that case, OpenJPA with PostgreSQL server is 78.1 times slower than EclipseLink with Derby embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded	OpenJPA PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	5.1	17.3	7.5	17.5	6.3	17.4
Element Collection Test	0.72	11.3	4.6	5.4	2.6	8.3
Inheritance Test	4.7	14.0	7.6	18.2	6.2	16.1
Indexing Test	6.3	8.4	9.7	27.2	8.0	17.8
Graph (Binary Tree) Test	0.59	2.2	0.50	2.6	0.55	2.4
Multithreading Test	18.7	21.2	12.2	13.9	15.5	17.6
All Tests	6.0	12.7	7.0	14.5	6.5	13.6

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

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 embedded database (11.3) reveals that in that case, EclipseLink with Derby embedded is 15.7 times faster than OpenJPA with PostgreSQL server.

JPA Performance Benchmark (JPAB)