• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

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

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
	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded
Basic Person Test	0.0047	30.4	1.8	29.1	0.90	29.7
Element Collection Test	0.0038	19.6	1.5	27.6	0.77	23.6
Inheritance Test	0.0035	33.8	2.2	39.8	1.1	36.8
Indexing Test	0.0043	22.2	1.8	41.3	0.89	31.8
Graph (Binary Tree) Test	failed	16.0	failed	20.0	failed	18.0
Multithreading Test	failed	33.7	failed	29.0	failed	31.4
All Tests	0.0041	25.9	1.8	31.1	0.91	28.5

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
	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded
Basic Person Test	failed	4.4	failed	1.4	failed	2.9
Element Collection Test	failed	4.1	failed	2.4	failed	3.2
Inheritance Test	failed	3.4	failed	2.0	failed	2.7
Indexing Test	failed	13.0	failed	22.8	failed	17.9
Multithreading Test	failed	1.0	failed	0.67	failed	0.85
All Tests	failed	5.2	failed	5.9	failed	5.5

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
	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded
Basic Person Test	0.012	16.6	0.76	7.6	0.39	12.1
Element Collection Test	0.012	15.3	1.1	10.5	0.53	12.9
Inheritance Test	0.011	15.7	0.81	9.8	0.41	12.7
Indexing Test	0.011	12.1	1.3	9.9	0.64	11.0
Graph (Binary Tree) Test	failed	13.7	failed	7.0	failed	10.3
Multithreading Test	failed	20.9	failed	4.2	failed	12.6
All Tests	0.012	15.7	0.97	8.2	0.49	12.0

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
	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded
Basic Person Test	0.011	35.1	1.5	19.6	0.74	27.4
Element Collection Test	0.010	19.3	1.6	8.5	0.80	13.9
Inheritance Test	0.0093	36.0	1.1	14.0	0.57	25.0
Indexing Test	0.017	42.5	2.1	19.2	1.1	30.9
Graph (Binary Tree) Test	failed	12.2	failed	14.4	failed	13.3
Multithreading Test	failed	54.4	failed	25.8	failed	40.1
All Tests	0.012	33.3	1.6	16.9	0.79	25.1

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
	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded	DataNucleus DB4O embedded	EclipseLink H2 embedded
Basic Person Test	35.1	36.2	35.4	39.2	35.2	37.7
Element Collection Test	29.5	33.3	29.9	34.9	29.7	34.1
Inheritance Test	33.4	35.4	33.5	36.2	33.4	35.8
Indexing Test	41.0	39.8	41.9	43.7	41.5	41.7
Graph (Binary Tree) Test	failed	41.0	failed	28.4	failed	34.7
Multithreading Test	failed	48.7	failed	12.4	failed	30.6
All Tests	34.8	39.1	35.2	32.5	35.0	35.8

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

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.