• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus with DB4O embedded vs EclipseLink with HSQLDB 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 HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded
Basic Person Test	0.059	27.1	1.3	17.2	0.69	22.2
Element Collection Test	0.045	17.2	1.0	8.2	0.52	12.7
Inheritance Test	0.051	26.7	0.85	11.9	0.45	19.3
Indexing Test	0.080	30.6	2.3	18.6	1.2	24.6
Graph (Binary Tree) Test	failed	20.0	failed	15.9	failed	18.0
Multithreading Test	failed	32.5	failed	11.4	failed	22.0
All Tests	0.059	25.7	1.4	13.9	0.71	19.8

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (19.8) reveals that in these tests, EclipseLink with HSQLDB embedded is 27.9 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 HSQLDB embedded database (26.7) reveals that in that case, EclipseLink with HSQLDB embedded is 524 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 HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded
Basic Person Test	0.0047	24.4	1.8	36.0	0.90	30.2
Element Collection Test	0.0038	14.9	1.5	19.1	0.77	17.0
Inheritance Test	0.0035	22.8	2.2	40.0	1.1	31.4
Indexing Test	0.0043	20.7	1.8	38.7	0.89	29.7
Graph (Binary Tree) Test	failed	8.7	failed	14.2	failed	11.4
Multithreading Test	failed	24.2	failed	28.0	failed	26.1
All Tests	0.0041	19.3	1.8	29.3	0.91	24.3

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (24.3) reveals that in these tests, EclipseLink with HSQLDB embedded is 26.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 retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0035) to the normalized speed of EclipseLink with HSQLDB embedded database (22.8) reveals that in that case, EclipseLink with HSQLDB embedded is 6,514 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 HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded
Basic Person Test	failed	2.9	failed	0.88	failed	1.9
Element Collection Test	failed	3.2	failed	1.4	failed	2.3
Inheritance Test	failed	2.6	failed	1.1	failed	1.9
Indexing Test	failed	21.5	failed	33.3	failed	27.4
Multithreading Test	failed	1.1	failed	0.52	failed	0.82
All Tests	failed	6.3	failed	7.4	failed	6.9

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 HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded
Basic Person Test	0.012	17.9	0.76	7.0	0.39	12.5
Element Collection Test	0.012	14.6	1.1	8.3	0.53	11.4
Inheritance Test	0.011	16.2	0.81	9.7	0.41	13.0
Indexing Test	0.011	12.0	1.3	6.8	0.64	9.4
Graph (Binary Tree) Test	failed	4.7	failed	3.4	failed	4.0
Multithreading Test	failed	24.4	failed	4.4	failed	14.4
All Tests	0.012	15.0	0.97	6.6	0.49	10.8

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (10.8) reveals that in these tests, EclipseLink with HSQLDB embedded is 22.0 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.012) to the normalized speed of EclipseLink with HSQLDB embedded database (17.9) reveals that in that case, EclipseLink with HSQLDB embedded is 1,492 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 HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded
Basic Person Test	0.011	32.3	1.5	20.3	0.74	26.3
Element Collection Test	0.010	14.3	1.6	6.0	0.80	10.2
Inheritance Test	0.0093	29.2	1.1	23.9	0.57	26.6
Indexing Test	0.017	55.3	2.1	27.1	1.1	41.2
Graph (Binary Tree) Test	failed	6.8	failed	14.1	failed	10.4
Multithreading Test	failed	52.9	failed	28.4	failed	40.6
All Tests	0.012	31.8	1.6	20.0	0.79	25.9

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (25.9) reveals that in these tests, EclipseLink with HSQLDB embedded is 32.8 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.017) to the normalized speed of EclipseLink with HSQLDB embedded database (55.3) reveals that in that case, EclipseLink with HSQLDB embedded is 3,253 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 HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded
Basic Person Test	35.1	41.4	35.4	41.4	35.2	41.4
Element Collection Test	29.5	46.9	29.9	46.9	29.7	46.9
Inheritance Test	33.4	41.4	33.5	41.4	33.4	41.4
Indexing Test	41.0	48.4	41.9	49.2	41.5	48.8
Graph (Binary Tree) Test	failed	28.5	failed	21.4	failed	25.0
Multithreading Test	failed	51.9	failed	10.3	failed	31.1
All Tests	34.8	43.1	35.2	35.1	35.0	39.1

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded
Basic Person Test	0.022	20.9	1.3	16.3	0.68	18.6
Element Collection Test	0.018	12.8	1.3	8.6	0.66	10.7
Inheritance Test	0.019	19.5	1.2	17.3	0.63	18.4
Indexing Test	0.028	28.0	1.9	24.9	0.94	26.5
Graph (Binary Tree) Test	failed	10.0	failed	11.9	failed	11.0
Multithreading Test	failed	27.0	failed	14.6	failed	20.8
All Tests	0.022	20.1	1.4	15.7	0.73	17.9

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (17.9) reveals that in these tests, EclipseLink with HSQLDB 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/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.019) to the normalized speed of EclipseLink with HSQLDB embedded database (19.5) reveals that in that case, EclipseLink with HSQLDB embedded is 1,026 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.