• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus with DB4O 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
	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded
Basic Person Test	0.059	19.2	1.3	8.0	0.69	13.6
Element Collection Test	0.045	6.6	1.0	2.8	0.52	4.7
Inheritance Test	0.051	15.6	0.85	4.4	0.45	10.0
Indexing Test	0.080	24.4	2.3	11.8	1.2	18.1
Graph (Binary Tree) Test	failed	9.2	failed	6.2	failed	7.7
Multithreading Test	failed	34.9	failed	7.1	failed	21.0
All Tests	0.059	18.3	1.4	6.7	0.71	12.5

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

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

A huge performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.059) to the normalized speed of DataNucleus with H2 embedded database (19.2) reveals that in that case, DataNucleus with H2 embedded is 325 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	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded
Basic Person Test	0.0047	13.2	1.8	13.5	0.90	13.3
Element Collection Test	0.0038	6.4	1.5	8.9	0.77	7.7
Inheritance Test	0.0035	12.2	2.2	12.7	1.1	12.4
Indexing Test	0.0043	8.1	1.8	16.5	0.89	12.3
Graph (Binary Tree) Test	failed	10.6	failed	20.9	failed	15.8
Multithreading Test	failed	13.3	failed	9.9	failed	11.6
All Tests	0.0041	10.6	1.8	13.7	0.91	12.2

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

The results above show that in general DataNucleus 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 DataNucleus with H2 embedded database (12.2) reveals that in these tests, DataNucleus with H2 embedded is 13.4 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 DataNucleus with H2 embedded database (12.2) reveals that in that case, DataNucleus with H2 embedded is 3,486 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	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded
Basic Person Test	failed	4.7	failed	1.4	failed	3.1
Element Collection Test	failed	5.0	failed	2.4	failed	3.7
Inheritance Test	failed	3.8	failed	1.6	failed	2.7
Indexing Test	failed	0.0041	failed	1.8	failed	0.91
Multithreading Test	failed	1.2	failed	0.79	failed	1.0
All Tests	failed	3.0	failed	1.6	failed	2.3

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	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded
Basic Person Test	0.012	10.0	0.76	3.9	0.39	6.9
Element Collection Test	0.012	7.6	1.1	3.9	0.53	5.8
Inheritance Test	0.011	9.4	0.81	4.4	0.41	6.9
Indexing Test	0.011	10.6	1.3	5.9	0.64	8.2
Graph (Binary Tree) Test	failed	5.9	failed	3.7	failed	4.8
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.012	8.7	0.97	4.4	0.49	6.5

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

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

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.011) to the normalized speed of DataNucleus with H2 embedded database (10.6) reveals that in that case, DataNucleus with H2 embedded is 964 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	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded
Basic Person Test	0.011	4.2	1.5	1.3	0.74	2.8
Element Collection Test	0.010	4.9	1.6	1.6	0.80	3.2
Inheritance Test	0.0093	4.0	1.1	1.3	0.57	2.7
Indexing Test	0.017	7.5	2.1	1.9	1.1	4.7
Graph (Binary Tree) Test	failed	5.6	failed	4.1	failed	4.8
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.012	5.2	1.6	2.0	0.79	3.6

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

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.010) to the normalized speed of DataNucleus with H2 embedded database (4.9) reveals that in that case, DataNucleus with H2 embedded is 490 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	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded
Basic Person Test	35.1	27.0	35.4	27.0	35.2	27.0
Element Collection Test	29.5	22.4	29.9	22.4	29.7	22.4
Inheritance Test	33.4	27.0	33.5	27.0	33.4	27.0
Indexing Test	41.0	31.6	41.9	32.1	41.5	31.9
Graph (Binary Tree) Test	failed	20.0	failed	15.0	failed	17.5
Multithreading Test	failed	33.9	failed	9.2	failed	21.5
All Tests	34.8	27.0	35.2	22.1	35.0	24.6

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

The results above show that in general DataNucleus with DB4O 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
	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded	DataNucleus DB4O embedded	DataNucleus H2 embedded
Basic Person Test	0.022	10.3	1.3	5.6	0.68	7.9
Element Collection Test	0.018	6.1	1.3	3.9	0.66	5.0
Inheritance Test	0.019	9.0	1.2	4.9	0.63	6.9
Indexing Test	0.028	10.1	1.9	7.6	0.94	8.9
Graph (Binary Tree) Test	failed	7.8	failed	8.7	failed	8.3
Multithreading Test	failed	16.5	failed	5.9	failed	11.2
All Tests	0.022	9.6	1.4	6.0	0.73	7.8

The results above show that in general DataNucleus 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 DataNucleus with H2 embedded database (7.8) reveals that in these tests, DataNucleus with H2 embedded is 10.7 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 DataNucleus with H2 embedded database (9.0) reveals that in that case, DataNucleus with H2 embedded is 474 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.