Comparison of EclipseLink with H2 embedded 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 H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server
Basic Person Test	25.1	5.2	8.9	4.8	17.0	5.0
Element Collection Test	20.4	2.8	8.0	2.2	14.2	2.5
Inheritance Test	28.7	4.6	8.7	3.2	18.7	3.9
Indexing Test	37.6	7.4	14.0	6.9	25.8	7.1
Graph (Binary Tree) Test	17.7	0.98	14.7	0.81	16.2	0.89
Multithreading Test	30.3	23.4	11.4	9.1	20.8	16.2
All Tests	26.6	7.4	10.9	4.5	18.8	5.9

The results above show that in general EclipseLink with H2 embedded is much more efficient than OpenJPA with PostgreSQL server in persisting JPA entity objects to the database. Comparing the normalized speed of OpenJPA with PostgreSQL database server (5.9) to the normalized speed of EclipseLink with H2 embedded database (18.8) reveals that in these tests, EclipseLink with H2 embedded is 3.2 times faster than OpenJPA with PostgreSQL server.

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server
Basic Person Test	30.4	5.8	29.1	16.1	29.7	10.9
Element Collection Test	19.6	0.013	27.6	8.7	23.6	4.4
Inheritance Test	33.8	5.2	39.8	17.6	36.8	11.4
Indexing Test	22.2	4.8	41.3	18.7	31.8	11.8
Graph (Binary Tree) Test	16.0	0.27	20.0	0.35	18.0	0.31
Multithreading Test	33.7	11.9	29.0	23.3	31.4	17.6
All Tests	25.9	4.7	31.1	14.1	28.5	9.4

The results above show that in general EclipseLink with H2 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 H2 embedded database (28.5) reveals that in these tests, EclipseLink with H2 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 H2 embedded database (19.6) reveals that in that case, EclipseLink with H2 embedded is 1,508 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
	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server
Basic Person Test	4.4	failed	1.4	failed	2.9	failed
Element Collection Test	4.1	failed	2.4	failed	3.2	failed
Inheritance Test	3.4	failed	2.0	failed	2.7	failed
Indexing Test	13.0	failed	22.8	failed	17.9	failed
Multithreading Test	1.0	failed	0.67	failed	0.85	failed
All Tests	5.2	failed	5.9	failed	5.5	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 H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server
Basic Person Test	16.6	4.9	7.6	3.9	12.1	4.4
Element Collection Test	15.3	0.033	10.5	4.6	12.9	2.3
Inheritance Test	15.7	4.8	9.8	4.9	12.7	4.9
Indexing Test	12.1	5.1	9.9	6.0	11.0	5.6
Graph (Binary Tree) Test	13.7	0.57	7.0	0.31	10.3	0.44
Multithreading Test	20.9	22.2	4.2	7.4	12.6	14.8
All Tests	15.7	6.3	8.2	4.5	12.0	5.4

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

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 H2 embedded database (15.3) reveals that in that case, EclipseLink with H2 embedded is 464 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
	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server
Basic Person Test	35.1	4.6	19.6	5.3	27.4	5.0
Element Collection Test	19.3	0.032	8.5	2.8	13.9	1.4
Inheritance Test	36.0	4.3	14.0	4.6	25.0	4.4
Indexing Test	42.5	8.0	19.2	7.1	30.9	7.5
Graph (Binary Tree) Test	12.2	0.53	14.4	0.55	13.3	0.54
Multithreading Test	54.4	17.4	25.8	9.1	40.1	13.3
All Tests	33.3	5.8	16.9	4.9	25.1	5.4

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

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.032) to the normalized speed of EclipseLink with H2 embedded database (19.3) reveals that in that case, EclipseLink with H2 embedded is 603 times faster than OpenJPA with PostgreSQL server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server	EclipseLink H2 embedded	OpenJPA PostgreSQL server
Basic Person Test	22.3	5.1	13.3	7.5	17.8	6.3
Element Collection Test	15.7	0.72	11.4	4.6	13.6	2.6
Inheritance Test	23.5	4.7	14.9	7.6	19.2	6.2
Indexing Test	25.5	6.3	21.5	9.7	23.5	8.0
Graph (Binary Tree) Test	14.9	0.59	14.0	0.50	14.5	0.55
Multithreading Test	28.1	18.7	14.2	12.2	21.1	15.5
All Tests	21.9	6.0	14.9	7.0	18.4	6.5

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

A huge performance gap has been detected when using graphs of objects with large transaction/retrieval size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.50) to the normalized speed of EclipseLink with H2 embedded database (14.0) reveals that in that case, EclipseLink with H2 embedded is 28.0 times faster than OpenJPA with PostgreSQL server.

JPA Performance Benchmark (JPAB)