Comparison of OpenJPA with Derby server vs EclipseLink with H2 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 Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded
Basic Person Test	3.1	25.1	2.7	8.9	2.9	17.0
Element Collection Test	2.0	20.4	1.7	8.0	1.8	14.2
Inheritance Test	3.0	28.7	2.3	8.7	2.6	18.7
Indexing Test	4.7	37.6	4.1	14.0	4.4	25.8
Graph (Binary Tree) Test	0.71	17.7	0.64	14.7	0.67	16.2
Multithreading Test	6.0	30.3	3.8	11.4	4.9	20.8
All Tests	3.3	26.6	2.5	10.9	2.9	18.8

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

A huge performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (0.71) to the normalized speed of EclipseLink with H2 embedded database (17.7) reveals that in that case, EclipseLink with H2 embedded is 24.9 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
	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded
Basic Person Test	0.78	30.4	11.6	29.1	6.2	29.7
Element Collection Test	0.0024	19.6	1.1	27.6	0.54	23.6
Inheritance Test	0.014	33.8	5.0	39.8	2.5	36.8
Indexing Test	0.62	22.2	13.0	41.3	6.8	31.8
Graph (Binary Tree) Test	0.065	16.0	0.39	20.0	0.23	18.0
Multithreading Test	1.6	33.7	19.0	29.0	10.3	31.4
All Tests	0.51	25.9	8.4	31.1	4.4	28.5

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

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with Derby database server (0.0024) to the normalized speed of EclipseLink with H2 embedded database (19.6) reveals that in that case, EclipseLink with H2 embedded is 8,167 times faster 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
	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded
Basic Person Test	29.2	4.4	5.5	1.4	17.3	2.9
Element Collection Test	2.2	4.1	1.4	2.4	1.8	3.2
Inheritance Test	2.2	3.4	1.0	2.0	1.6	2.7
Indexing Test	2.2	13.0	11.7	22.8	7.0	17.9
Multithreading Test	35.5	1.0	8.3	0.67	21.9	0.85
All Tests	14.3	5.2	5.6	5.9	9.9	5.5

The results above show that in general OpenJPA with Derby server is more efficient than EclipseLink with H2 embedded in executing the tested JPA queries.

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

On the other hand, OpenJPA with Derby server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of OpenJPA with Derby database server (2.2) to the normalized speed of EclipseLink with H2 embedded database (13.0) reveals that in that case, OpenJPA with Derby server is 5.9 times slower than EclipseLink with H2 embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded
Basic Person Test	1.5	16.6	4.0	7.6	2.8	12.1
Element Collection Test	0.0081	15.3	1.9	10.5	0.94	12.9
Inheritance Test	0.043	15.7	3.8	9.8	1.9	12.7
Indexing Test	1.8	12.1	6.8	9.9	4.3	11.0
Graph (Binary Tree) Test	0.16	13.7	0.27	7.0	0.22	10.3
Multithreading Test	6.9	20.9	5.0	4.2	5.9	12.6
All Tests	1.7	15.7	3.6	8.2	2.7	12.0

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (0.0081) to the normalized speed of EclipseLink with H2 embedded database (15.3) reveals that in that case, EclipseLink with H2 embedded is 1,889 times faster 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
	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded
Basic Person Test	1.4	35.1	3.7	19.6	2.5	27.4
Element Collection Test	0.0082	19.3	1.4	8.5	0.71	13.9
Inheritance Test	0.035	36.0	2.5	14.0	1.3	25.0
Indexing Test	2.3	42.5	3.5	19.2	2.9	30.9
Graph (Binary Tree) Test	0.13	12.2	0.35	14.4	0.24	13.3
Multithreading Test	3.6	54.4	4.0	25.8	3.8	40.1
All Tests	1.3	33.3	2.6	16.9	1.9	25.1

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (0.0082) to the normalized speed of EclipseLink with H2 embedded database (19.3) reveals that in that case, EclipseLink with H2 embedded is 2,354 times faster 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
	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded	OpenJPA Derby server	EclipseLink H2 embedded
Basic Person Test	7.2	22.3	5.5	13.3	6.4	17.8
Element Collection Test	0.84	15.7	1.5	11.4	1.2	13.6
Inheritance Test	1.1	23.5	2.9	14.9	2.0	19.2
Indexing Test	2.3	25.5	7.8	21.5	5.1	23.5
Graph (Binary Tree) Test	0.27	14.9	0.41	14.0	0.34	14.5
Multithreading Test	10.7	28.1	8.0	14.2	9.4	21.1
All Tests	3.9	21.9	4.5	14.9	4.2	18.4

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

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

JPA Performance Benchmark (JPAB)