Comparison of EclipseLink with Derby embedded 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
	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded
Basic Person Test	5.5	25.1	3.7	8.9	4.6	17.0
Element Collection Test	3.0	20.4	1.7	8.0	2.4	14.2
Inheritance Test	5.3	28.7	3.5	8.7	4.4	18.7
Indexing Test	6.9	37.6	4.6	14.0	5.8	25.8
Graph (Binary Tree) Test	2.0	17.7	1.9	14.7	1.9	16.2
Multithreading Test	9.3	30.3	4.1	11.4	6.7	20.8
All Tests	5.3	26.6	3.2	10.9	4.3	18.8

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

A large performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (2.0) to the normalized speed of EclipseLink with H2 embedded database (17.7) reveals that in that case, EclipseLink with H2 embedded is 8.8 times faster 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
	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded
Basic Person Test	16.4	30.4	58.7	29.1	37.5	29.7
Element Collection Test	7.5	19.6	13.3	27.6	10.4	23.6
Inheritance Test	17.1	33.8	58.9	39.8	38.0	36.8
Indexing Test	14.2	22.2	67.4	41.3	40.8	31.8
Graph (Binary Tree) Test	2.8	16.0	5.7	20.0	4.2	18.0
Multithreading Test	28.0	33.7	48.7	29.0	38.4	31.4
All Tests	14.3	25.9	42.1	31.1	28.2	28.5

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

A large performance gap has been detected when using graphs of objects with small retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (2.8) to the normalized speed of EclipseLink with H2 embedded database (16.0) reveals that in that case, EclipseLink with H2 embedded is 5.7 times faster than EclipseLink with Derby embedded.

On the other hand, EclipseLink with H2 embedded is slower, for instance, when using simple basic entities with large retrieval size. Comparing the normalized speed of EclipseLink with H2 embedded database (29.1) to the normalized speed of EclipseLink with Derby embedded database (58.7) reveals that in that case, EclipseLink with H2 embedded is 2.0 times slower than EclipseLink with Derby embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded
Basic Person Test	53.4	4.4	13.8	1.4	33.6	2.9
Element Collection Test	37.9	4.1	4.4	2.4	21.2	3.2
Inheritance Test	37.4	3.4	15.0	2.0	26.2	2.7
Indexing Test	7.6	13.0	49.3	22.8	28.4	17.9
Multithreading Test	41.2	1.0	6.1	0.67	23.6	0.85
All Tests	35.5	5.2	17.7	5.9	26.6	5.5

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

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 EclipseLink with Derby embedded database (41.2) reveals that in that case, EclipseLink with Derby embedded is 41.2 times faster 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
	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded
Basic Person Test	6.4	16.6	6.7	7.6	6.5	12.1
Element Collection Test	5.4	15.3	6.2	10.5	5.8	12.9
Inheritance Test	6.5	15.7	9.2	9.8	7.8	12.7
Indexing Test	7.3	12.1	11.1	9.9	9.2	11.0
Graph (Binary Tree) Test	2.8	13.7	1.7	7.0	2.2	10.3
Multithreading Test	21.3	20.9	5.0	4.2	13.1	12.6
All Tests	8.3	15.7	6.6	8.2	7.5	12.0

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded
Basic Person Test	4.6	35.1	4.7	19.6	4.6	27.4
Element Collection Test	2.5	19.3	1.4	8.5	1.9	13.9
Inheritance Test	3.9	36.0	4.5	14.0	4.2	25.0
Indexing Test	6.2	42.5	3.8	19.2	5.0	30.9
Graph (Binary Tree) Test	1.1	12.2	1.0	14.4	1.1	13.3
Multithreading Test	6.2	54.4	5.8	25.8	6.0	40.1
All Tests	4.1	33.3	3.5	16.9	3.8	25.1

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

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

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded
Basic Person Test	51.1	36.2	51.0	39.2	51.1	37.7
Element Collection Test	38.5	33.3	39.4	34.9	38.9	34.1
Inheritance Test	48.0	35.4	47.9	36.2	48.0	35.8
Indexing Test	51.6	39.8	52.3	43.7	52.0	41.7
Graph (Binary Tree) Test	13.4	41.0	11.7	28.4	12.6	34.7
Multithreading Test	52.6	48.7	8.4	12.4	30.5	30.6
All Tests	42.5	39.1	35.1	32.5	38.8	35.8

The results above show that in general EclipseLink with Derby embedded is slightly more efficient than EclipseLink with H2 embedded in using disk space.

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized score of EclipseLink with Derby embedded database (13.4) to the normalized score of EclipseLink with H2 embedded database (41.0) reveals that in that case, EclipseLink with Derby embedded is 3.1 times less efficient than EclipseLink with H2 embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded	EclipseLink Derby embedded	EclipseLink H2 embedded
Basic Person Test	17.3	22.3	17.5	13.3	17.4	17.8
Element Collection Test	11.3	15.7	5.4	11.4	8.3	13.6
Inheritance Test	14.0	23.5	18.2	14.9	16.1	19.2
Indexing Test	8.4	25.5	27.2	21.5	17.8	23.5
Graph (Binary Tree) Test	2.2	14.9	2.6	14.0	2.4	14.5
Multithreading Test	21.2	28.1	13.9	14.2	17.6	21.1
All Tests	12.7	21.9	14.5	14.9	13.6	18.4

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

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

JPA Performance Benchmark (JPAB)