• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus 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
	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded
Basic Person Test	4.6	25.1	2.8	8.9	3.7	17.0
Element Collection Test	2.4	20.4	1.6	8.0	2.0	14.2
Inheritance Test	4.6	28.7	2.7	8.7	3.7	18.7
Indexing Test	7.6	37.6	4.8	14.0	6.2	25.8
Graph (Binary Tree) Test	1.6	17.7	1.4	14.7	1.5	16.2
Multithreading Test	8.6	30.3	3.3	11.4	5.9	20.8
All Tests	4.9	26.6	2.8	10.9	3.8	18.8

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded
Basic Person Test	6.8	30.4	14.9	29.1	10.9	29.7
Element Collection Test	5.4	19.6	7.6	27.6	6.5	23.6
Inheritance Test	8.8	33.8	14.8	39.8	11.8	36.8
Indexing Test	9.2	22.2	14.1	41.3	11.6	31.8
Graph (Binary Tree) Test	9.9	16.0	15.8	20.0	12.9	18.0
Multithreading Test	11.9	33.7	11.5	29.0	11.7	31.4
All Tests	8.7	25.9	13.1	31.1	10.9	28.5

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded
Basic Person Test	39.1	4.4	7.5	1.4	23.3	2.9
Element Collection Test	46.0	4.1	6.7	2.4	26.3	3.2
Inheritance Test	7.7	3.4	3.8	2.0	5.7	2.7
Indexing Test	0.053	13.0	8.0	22.8	4.0	17.9
Multithreading Test	failed	1.0	failed	0.67	failed	0.85
All Tests	23.2	5.2	6.5	5.9	14.8	5.5

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

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

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of EclipseLink with H2 embedded database (4.1) to the normalized speed of DataNucleus with Derby embedded database (46.0) reveals that in that case, DataNucleus with Derby embedded is 11.2 times faster than EclipseLink with H2 embedded.

On the other hand, DataNucleus with Derby embedded is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (0.053) to the normalized speed of EclipseLink with H2 embedded database (13.0) reveals that in that case, DataNucleus with Derby embedded is 245 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
	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded
Basic Person Test	4.0	16.6	3.8	7.6	3.9	12.1
Element Collection Test	3.7	15.3	4.5	10.5	4.1	12.9
Inheritance Test	4.4	15.7	4.8	9.8	4.6	12.7
Indexing Test	5.2	12.1	4.2	9.9	4.7	11.0
Graph (Binary Tree) Test	2.7	13.7	1.5	7.0	2.1	10.3
Multithreading Test	failed	20.9	failed	4.2	failed	12.6
All Tests	4.0	15.7	3.7	8.2	3.9	12.0

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

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded
Basic Person Test	3.5	35.1	1.3	19.6	2.4	27.4
Element Collection Test	1.9	19.3	1.6	8.5	1.7	13.9
Inheritance Test	2.4	36.0	1.3	14.0	1.9	25.0
Indexing Test	6.6	42.5	1.9	19.2	4.3	30.9
Graph (Binary Tree) Test	0.81	12.2	0.93	14.4	0.87	13.3
Multithreading Test	failed	54.4	failed	25.8	failed	40.1
All Tests	3.0	33.3	1.4	16.9	2.2	25.1

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

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded
Basic Person Test	53.3	36.2	53.3	39.2	53.3	37.7
Element Collection Test	42.6	33.3	42.6	34.9	42.6	34.1
Inheritance Test	48.1	35.4	48.1	36.2	48.1	35.8
Indexing Test	62.3	39.8	63.3	43.7	62.8	41.7
Graph (Binary Tree) Test	13.6	41.0	10.2	28.4	11.9	34.7
Multithreading Test	52.0	48.7	8.0	12.4	30.0	30.6
All Tests	45.3	39.1	37.6	32.5	41.5	35.8

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

On the other hand, DataNucleus with Derby embedded is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized score of DataNucleus with Derby embedded database (13.6) to the normalized score of EclipseLink with H2 embedded database (41.0) reveals that in that case, DataNucleus with Derby embedded is 3.0 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
	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded
Basic Person Test	11.6	22.3	6.1	13.3	8.8	17.8
Element Collection Test	11.9	15.7	4.4	11.4	8.1	13.6
Inheritance Test	5.6	23.5	5.5	14.9	5.5	19.2
Indexing Test	5.7	25.5	6.6	21.5	6.2	23.5
Graph (Binary Tree) Test	3.7	14.9	4.9	14.0	4.3	14.5
Multithreading Test	10.3	28.1	7.4	14.2	8.8	21.1
All Tests	8.0	21.9	5.7	14.9	6.9	18.4

The results above show that in general EclipseLink with H2 embedded is more efficient than DataNucleus with Derby embedded in performing JPA database operations. Comparing the normalized speed of DataNucleus with Derby embedded database (6.9) to the normalized speed of EclipseLink with H2 embedded database (18.4) reveals that in these tests, EclipseLink with H2 embedded is 2.7 times faster than DataNucleus with Derby embedded.

A large performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (5.7) to the normalized speed of EclipseLink with H2 embedded database (25.5) reveals that in that case, EclipseLink with H2 embedded is 4.5 times faster than DataNucleus with Derby embedded.

Other Head to Head DBMS/JPA Comparisons

JPA Performance Benchmark - Copyright © 2010, 2011, 2012 ObjectDB Software Ltd. - All rights reserved.
The benchmark program is released as open source under the GPL license.