Comparison of EclipseLink with Derby embedded vs DataNucleus 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	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded
Basic Person Test	5.5	19.2	3.7	8.0	4.6	13.6
Element Collection Test	3.0	6.6	1.7	2.8	2.4	4.7
Inheritance Test	5.3	15.6	3.5	4.4	4.4	10.0
Indexing Test	6.9	24.4	4.6	11.8	5.8	18.1
Graph (Binary Tree) Test	2.0	9.2	1.9	6.2	1.9	7.7
Multithreading Test	9.3	34.9	4.1	7.1	6.7	21.0
All Tests	5.3	18.3	3.2	6.7	4.3	12.5

The results above show that in general DataNucleus with H2 embedded is 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 DataNucleus with H2 embedded database (12.5) reveals that in these tests, DataNucleus with H2 embedded is 2.9 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 DataNucleus with H2 embedded database (9.2) reveals that in that case, DataNucleus with H2 embedded is 4.6 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	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded
Basic Person Test	16.4	13.2	58.7	13.5	37.5	13.3
Element Collection Test	7.5	6.4	13.3	8.9	10.4	7.7
Inheritance Test	17.1	12.2	58.9	12.7	38.0	12.4
Indexing Test	14.2	8.1	67.4	16.5	40.8	12.3
Graph (Binary Tree) Test	2.8	10.6	5.7	20.9	4.2	15.8
Multithreading Test	28.0	13.3	48.7	9.9	38.4	11.6
All Tests	14.3	10.6	42.1	13.7	28.2	12.2

The results above show that in general EclipseLink with Derby embedded is more efficient than DataNucleus with H2 embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with H2 embedded database (12.2) to the normalized speed of EclipseLink with Derby embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 2.3 times faster than DataNucleus with H2 embedded.

A large performance gap has been detected when using multithreading with large retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (9.9) to the normalized speed of EclipseLink with Derby embedded database (48.7) reveals that in that case, EclipseLink with Derby embedded is 4.9 times faster than DataNucleus with H2 embedded.

On the other hand, EclipseLink with Derby embedded is slower, for instance, 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 DataNucleus with H2 embedded database (10.6) reveals that in that case, EclipseLink with Derby embedded is 3.8 times slower than DataNucleus with H2 embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded
Basic Person Test	53.4	4.7	13.8	1.4	33.6	3.1
Element Collection Test	37.9	5.0	4.4	2.4	21.2	3.7
Inheritance Test	37.4	3.8	15.0	1.6	26.2	2.7
Indexing Test	7.6	0.0041	49.3	1.8	28.4	0.91
Multithreading Test	41.2	1.2	6.1	0.79	23.6	1.0
All Tests	35.5	3.0	17.7	1.6	26.6	2.3

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

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (0.0041) to the normalized speed of EclipseLink with Derby embedded database (7.6) reveals that in that case, EclipseLink with Derby embedded is 1,854 times faster than DataNucleus 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	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded
Basic Person Test	6.4	10.0	6.7	3.9	6.5	6.9
Element Collection Test	5.4	7.6	6.2	3.9	5.8	5.8
Inheritance Test	6.5	9.4	9.2	4.4	7.8	6.9
Indexing Test	7.3	10.6	11.1	5.9	9.2	8.2
Graph (Binary Tree) Test	2.8	5.9	1.7	3.7	2.2	4.8
Multithreading Test	21.3	failed	5.0	failed	13.1	failed
All Tests	8.3	8.7	6.6	4.4	7.5	6.5

DataNucleus with H2 embedded has failed in 2 tests (see exceptions).

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

A large performance gap has been detected when using class inheritance in the object model with large transaction size. Comparing the normalized speed of DataNucleus with H2 embedded database (4.4) to the normalized speed of EclipseLink with Derby embedded database (9.2) reveals that in that case, EclipseLink with Derby embedded is 2.1 times faster than DataNucleus with H2 embedded.

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using graphs of objects with large transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (1.7) to the normalized speed of DataNucleus with H2 embedded database (3.7) reveals that in that case, EclipseLink with Derby embedded is 2.2 times slower than DataNucleus with H2 embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded
Basic Person Test	4.6	4.2	4.7	1.3	4.6	2.8
Element Collection Test	2.5	4.9	1.4	1.6	1.9	3.2
Inheritance Test	3.9	4.0	4.5	1.3	4.2	2.7
Indexing Test	6.2	7.5	3.8	1.9	5.0	4.7
Graph (Binary Tree) Test	1.1	5.6	1.0	4.1	1.1	4.8
Multithreading Test	6.2	failed	5.8	failed	6.0	failed
All Tests	4.1	5.2	3.5	2.0	3.8	3.6

DataNucleus with H2 embedded has failed in 2 tests (see exceptions).

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

A large performance gap has been detected when using simple basic entities with large transaction size. Comparing the normalized speed of DataNucleus with H2 embedded database (1.3) to the normalized speed of EclipseLink with Derby embedded database (4.7) reveals that in that case, EclipseLink with Derby embedded is 3.6 times faster than DataNucleus with H2 embedded.

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (1.1) to the normalized speed of DataNucleus with H2 embedded database (5.6) reveals that in that case, EclipseLink with Derby embedded is 5.1 times slower than DataNucleus with H2 embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded
Basic Person Test	51.1	27.0	51.0	27.0	51.1	27.0
Element Collection Test	38.5	22.4	39.4	22.4	38.9	22.4
Inheritance Test	48.0	27.0	47.9	27.0	48.0	27.0
Indexing Test	51.6	31.6	52.3	32.1	52.0	31.9
Graph (Binary Tree) Test	13.4	20.0	11.7	15.0	12.6	17.5
Multithreading Test	52.6	33.9	8.4	9.2	30.5	21.5
All Tests	42.5	27.0	35.1	22.1	38.8	24.6

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

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded	EclipseLink Derby embedded	DataNucleus H2 embedded
Basic Person Test	17.3	10.3	17.5	5.6	17.4	7.9
Element Collection Test	11.3	6.1	5.4	3.9	8.3	5.0
Inheritance Test	14.0	9.0	18.2	4.9	16.1	6.9
Indexing Test	8.4	10.1	27.2	7.6	17.8	8.9
Graph (Binary Tree) Test	2.2	7.8	2.6	8.7	2.4	8.3
Multithreading Test	21.2	16.5	13.9	5.9	17.6	11.2
All Tests	12.7	9.6	14.5	6.0	13.6	7.8

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

A large performance gap has been detected when using class inheritance in the object model with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (4.9) to the normalized speed of EclipseLink with Derby embedded database (18.2) reveals that in that case, EclipseLink with Derby embedded is 3.7 times faster than DataNucleus with H2 embedded.

On the other hand, EclipseLink with Derby embedded is slower, for instance, 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 DataNucleus with H2 embedded database (7.8) reveals that in that case, EclipseLink with Derby embedded is 3.5 times slower than DataNucleus with H2 embedded.

JPA Performance Benchmark (JPAB)