• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with H2 embedded vs DataNucleus with DB4O 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 DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded
Basic Person Test	25.1	0.059	8.9	1.3	17.0	0.69
Element Collection Test	20.4	0.045	8.0	1.0	14.2	0.52
Inheritance Test	28.7	0.051	8.7	0.85	18.7	0.45
Indexing Test	37.6	0.080	14.0	2.3	25.8	1.2
Graph (Binary Tree) Test	17.7	failed	14.7	failed	16.2	failed
Multithreading Test	30.3	failed	11.4	failed	20.8	failed
All Tests	26.6	0.059	10.9	1.4	18.8	0.71

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.051) to the normalized speed of EclipseLink with H2 embedded database (28.7) reveals that in that case, EclipseLink with H2 embedded is 563 times faster than DataNucleus with DB4O 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 DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded
Basic Person Test	30.4	0.0047	29.1	1.8	29.7	0.90
Element Collection Test	19.6	0.0038	27.6	1.5	23.6	0.77
Inheritance Test	33.8	0.0035	39.8	2.2	36.8	1.1
Indexing Test	22.2	0.0043	41.3	1.8	31.8	0.89
Graph (Binary Tree) Test	16.0	failed	20.0	failed	18.0	failed
Multithreading Test	33.7	failed	29.0	failed	31.4	failed
All Tests	25.9	0.0041	31.1	1.8	28.5	0.91

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0035) to the normalized speed of EclipseLink with H2 embedded database (33.8) reveals that in that case, EclipseLink with H2 embedded is 9,657 times faster than DataNucleus with DB4O 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 DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded
Basic Person Test	4.4	failed	1.4	failed	2.9	failed
Element Collection Test	4.1	failed	2.4	failed	3.2	failed
Inheritance Test	3.4	failed	2.0	failed	2.7	failed
Indexing Test	13.0	failed	22.8	failed	17.9	failed
Multithreading Test	1.0	failed	0.67	failed	0.85	failed
All Tests	5.2	failed	5.9	failed	5.5	failed

DataNucleus with DB4O embedded has failed in 10 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded
Basic Person Test	16.6	0.012	7.6	0.76	12.1	0.39
Element Collection Test	15.3	0.012	10.5	1.1	12.9	0.53
Inheritance Test	15.7	0.011	9.8	0.81	12.7	0.41
Indexing Test	12.1	0.011	9.9	1.3	11.0	0.64
Graph (Binary Tree) Test	13.7	failed	7.0	failed	10.3	failed
Multithreading Test	20.9	failed	4.2	failed	12.6	failed
All Tests	15.7	0.012	8.2	0.97	12.0	0.49

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.011) to the normalized speed of EclipseLink with H2 embedded database (15.7) reveals that in that case, EclipseLink with H2 embedded is 1,427 times faster than DataNucleus with DB4O 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 DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded
Basic Person Test	35.1	0.011	19.6	1.5	27.4	0.74
Element Collection Test	19.3	0.010	8.5	1.6	13.9	0.80
Inheritance Test	36.0	0.0093	14.0	1.1	25.0	0.57
Indexing Test	42.5	0.017	19.2	2.1	30.9	1.1
Graph (Binary Tree) Test	12.2	failed	14.4	failed	13.3	failed
Multithreading Test	54.4	failed	25.8	failed	40.1	failed
All Tests	33.3	0.012	16.9	1.6	25.1	0.79

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0093) to the normalized speed of EclipseLink with H2 embedded database (36.0) reveals that in that case, EclipseLink with H2 embedded is 3,871 times faster than DataNucleus with DB4O embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded
Basic Person Test	36.2	35.1	39.2	35.4	37.7	35.2
Element Collection Test	33.3	29.5	34.9	29.9	34.1	29.7
Inheritance Test	35.4	33.4	36.2	33.5	35.8	33.4
Indexing Test	39.8	41.0	43.7	41.9	41.7	41.5
Graph (Binary Tree) Test	41.0	failed	28.4	failed	34.7	failed
Multithreading Test	48.7	failed	12.4	failed	30.6	failed
All Tests	39.1	34.8	32.5	35.2	35.8	35.0

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general EclipseLink with H2 embedded is slightly more efficient than DataNucleus with DB4O 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 H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded
Basic Person Test	22.3	0.022	13.3	1.3	17.8	0.68
Element Collection Test	15.7	0.018	11.4	1.3	13.6	0.66
Inheritance Test	23.5	0.019	14.9	1.2	19.2	0.63
Indexing Test	25.5	0.028	21.5	1.9	23.5	0.94
Graph (Binary Tree) Test	14.9	failed	14.0	failed	14.5	failed
Multithreading Test	28.1	failed	14.2	failed	21.1	failed
All Tests	21.9	0.022	14.9	1.4	18.4	0.73

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.019) to the normalized speed of EclipseLink with H2 embedded database (23.5) reveals that in that case, EclipseLink with H2 embedded is 1,237 times faster than DataNucleus with DB4O 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.