Comparison of EclipseLink with H2 server vs OpenJPA 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
	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded
Basic Person Test	5.6	4.8	2.5	2.9	4.0	3.9
Element Collection Test	4.2	2.8	1.5	1.9	2.8	2.4
Inheritance Test	6.6	4.1	2.1	2.4	4.4	3.3
Indexing Test	9.7	6.1	4.1	4.1	6.9	5.1
Graph (Binary Tree) Test	4.7	1.5	3.5	1.4	4.1	1.4
Multithreading Test	10.2	8.7	4.0	3.3	7.1	6.0
All Tests	6.8	4.7	2.9	2.7	4.9	3.7

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

A large performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of OpenJPA with Derby embedded database (1.5) to the normalized speed of EclipseLink with H2 database server (4.7) reveals that in that case, EclipseLink with H2 server is 3.1 times faster than OpenJPA with Derby embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded
Basic Person Test	5.5	14.8	8.2	22.6	6.8	18.7
Element Collection Test	3.2	0.0031	4.2	2.3	3.7	1.2
Inheritance Test	4.7	0.015	10.1	7.0	7.4	3.5
Indexing Test	4.4	11.7	9.4	26.5	6.9	19.1
Graph (Binary Tree) Test	1.1	0.93	1.9	1.2	1.5	1.1
Multithreading Test	12.2	25.2	15.9	28.6	14.0	26.9
All Tests	5.2	8.8	8.3	14.7	6.7	11.7

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

A large performance gap has been detected when using database indexes with large retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (9.4) to the normalized speed of OpenJPA with Derby embedded database (26.5) reveals that in that case, OpenJPA with Derby embedded is 2.8 times faster than EclipseLink with H2 server.

On the other hand, OpenJPA with Derby embedded is slower, for instance, when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with Derby embedded database (0.0031) to the normalized speed of EclipseLink with H2 database server (3.2) reveals that in that case, OpenJPA with Derby embedded is 1,032 times slower than EclipseLink with H2 server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded
Basic Person Test	3.8	49.7	1.1	9.9	2.5	29.8
Element Collection Test	4.1	2.7	1.1	9.6	2.6	6.1
Inheritance Test	3.2	2.3	1.3	1.3	2.3	1.8
Indexing Test	3.0	7.0	8.0	17.1	5.5	12.1
Multithreading Test	1.1	40.9	1.0	11.7	1.1	26.3
All Tests	3.0	20.5	2.5	9.9	2.8	15.2

The results above show that in general OpenJPA with Derby embedded is much more efficient than EclipseLink with H2 server in executing the tested JPA queries. Comparing the normalized speed of EclipseLink with H2 database server (2.8) to the normalized speed of OpenJPA with Derby embedded database (15.2) reveals that in these tests, OpenJPA with Derby embedded is 5.4 times faster than EclipseLink with H2 server.

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded
Basic Person Test	4.5	5.6	2.2	5.2	3.4	5.4
Element Collection Test	3.8	0.0090	2.4	2.2	3.1	1.1
Inheritance Test	4.4	0.045	3.0	4.6	3.7	2.3
Indexing Test	4.2	6.1	3.1	8.7	3.7	7.4
Graph (Binary Tree) Test	1.4	1.6	0.79	0.91	1.1	1.3
Multithreading Test	7.8	18.3	2.5	4.5	5.1	11.4
All Tests	4.3	5.3	2.3	4.4	3.3	4.8

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

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

On the other hand, OpenJPA with Derby embedded is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with Derby embedded database (0.0090) to the normalized speed of EclipseLink with H2 database server (3.8) reveals that in that case, OpenJPA with Derby embedded is 422 times slower than EclipseLink with H2 server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded
Basic Person Test	6.4	4.2	3.1	4.5	4.8	4.3
Element Collection Test	3.0	0.0071	1.3	1.6	2.2	0.80
Inheritance Test	5.6	0.035	2.8	3.0	4.2	1.5
Indexing Test	10.3	5.3	3.8	3.6	7.0	4.4
Graph (Binary Tree) Test	1.5	0.80	1.3	0.93	1.4	0.86
Multithreading Test	7.0	5.7	4.9	6.2	6.0	6.0
All Tests	5.6	2.7	2.9	3.3	4.3	3.0

The results above show that in general EclipseLink with H2 server is more efficient than OpenJPA with Derby embedded in deleting JPA entity objects from 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 Derby embedded database (0.0071) to the normalized speed of EclipseLink with H2 database server (3.0) reveals that in that case, EclipseLink with H2 server is 423 times faster than OpenJPA with Derby embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded	EclipseLink H2 server	OpenJPA Derby embedded
Basic Person Test	5.2	15.8	3.4	9.0	4.3	12.4
Element Collection Test	3.6	1.1	2.1	3.5	2.9	2.3
Inheritance Test	4.9	1.3	3.9	3.7	4.4	2.5
Indexing Test	6.3	7.2	5.7	12.0	6.0	9.6
Graph (Binary Tree) Test	2.1	1.2	1.9	1.1	2.0	1.2
Multithreading Test	7.7	19.8	5.7	10.9	6.7	15.3
All Tests	5.1	8.0	3.8	6.9	4.5	7.4

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

A large performance gap has been detected when using simple basic entities with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (5.2) to the normalized speed of OpenJPA with Derby embedded database (15.8) reveals that in that case, OpenJPA with Derby embedded is 3.0 times faster than EclipseLink with H2 server.

On the other hand, OpenJPA with Derby embedded is slower, for instance, when using class inheritance in the object model with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with Derby embedded database (1.3) to the normalized speed of EclipseLink with H2 database server (4.9) reveals that in that case, OpenJPA with Derby embedded is 3.8 times slower than EclipseLink with H2 server.

JPA Performance Benchmark (JPAB)