• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with H2 embedded vs DataNucleus 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 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded
Basic Person Test	25.1	4.6	8.9	2.8	17.0	3.7
Element Collection Test	20.4	2.4	8.0	1.6	14.2	2.0
Inheritance Test	28.7	4.6	8.7	2.7	18.7	3.7
Indexing Test	37.6	7.6	14.0	4.8	25.8	6.2
Graph (Binary Tree) Test	17.7	1.6	14.7	1.4	16.2	1.5
Multithreading Test	30.3	8.6	11.4	3.3	20.8	5.9
All Tests	26.6	4.9	10.9	2.8	18.8	3.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
	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded
Basic Person Test	30.4	6.8	29.1	14.9	29.7	10.9
Element Collection Test	19.6	5.4	27.6	7.6	23.6	6.5
Inheritance Test	33.8	8.8	39.8	14.8	36.8	11.8
Indexing Test	22.2	9.2	41.3	14.1	31.8	11.6
Graph (Binary Tree) Test	16.0	9.9	20.0	15.8	18.0	12.9
Multithreading Test	33.7	11.9	29.0	11.5	31.4	11.7
All Tests	25.9	8.7	31.1	13.1	28.5	10.9

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
	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded
Basic Person Test	4.4	39.1	1.4	7.5	2.9	23.3
Element Collection Test	4.1	46.0	2.4	6.7	3.2	26.3
Inheritance Test	3.4	7.7	2.0	3.8	2.7	5.7
Indexing Test	13.0	0.053	22.8	8.0	17.9	4.0
Multithreading Test	1.0	failed	0.67	failed	0.85	failed
All Tests	5.2	23.2	5.9	6.5	5.5	14.8

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
	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded
Basic Person Test	16.6	4.0	7.6	3.8	12.1	3.9
Element Collection Test	15.3	3.7	10.5	4.5	12.9	4.1
Inheritance Test	15.7	4.4	9.8	4.8	12.7	4.6
Indexing Test	12.1	5.2	9.9	4.2	11.0	4.7
Graph (Binary Tree) Test	13.7	2.7	7.0	1.5	10.3	2.1
Multithreading Test	20.9	failed	4.2	failed	12.6	failed
All Tests	15.7	4.0	8.2	3.7	12.0	3.9

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
	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded
Basic Person Test	35.1	3.5	19.6	1.3	27.4	2.4
Element Collection Test	19.3	1.9	8.5	1.6	13.9	1.7
Inheritance Test	36.0	2.4	14.0	1.3	25.0	1.9
Indexing Test	42.5	6.6	19.2	1.9	30.9	4.3
Graph (Binary Tree) Test	12.2	0.81	14.4	0.93	13.3	0.87
Multithreading Test	54.4	failed	25.8	failed	40.1	failed
All Tests	33.3	3.0	16.9	1.4	25.1	2.2

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
	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded
Basic Person Test	36.2	53.3	39.2	53.3	37.7	53.3
Element Collection Test	33.3	42.6	34.9	42.6	34.1	42.6
Inheritance Test	35.4	48.1	36.2	48.1	35.8	48.1
Indexing Test	39.8	62.3	43.7	63.3	41.7	62.8
Graph (Binary Tree) Test	41.0	13.6	28.4	10.2	34.7	11.9
Multithreading Test	48.7	52.0	12.4	8.0	30.6	30.0
All Tests	39.1	45.3	32.5	37.6	35.8	41.5

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
	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded	EclipseLink H2 embedded	DataNucleus Derby embedded
Basic Person Test	22.3	11.6	13.3	6.1	17.8	8.8
Element Collection Test	15.7	11.9	11.4	4.4	13.6	8.1
Inheritance Test	23.5	5.6	14.9	5.5	19.2	5.5
Indexing Test	25.5	5.7	21.5	6.6	23.5	6.2
Graph (Binary Tree) Test	14.9	3.7	14.0	4.9	14.5	4.3
Multithreading Test	28.1	10.3	14.2	7.4	21.1	8.8
All Tests	21.9	8.0	14.9	5.7	18.4	6.9

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.