• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

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

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
	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded
Basic Person Test	24.4	0.0047	36.0	1.8	30.2	0.90
Element Collection Test	14.9	0.0038	19.1	1.5	17.0	0.77
Inheritance Test	22.8	0.0035	40.0	2.2	31.4	1.1
Indexing Test	20.7	0.0043	38.7	1.8	29.7	0.89
Graph (Binary Tree) Test	8.7	failed	14.2	failed	11.4	failed
Multithreading Test	24.2	failed	28.0	failed	26.1	failed
All Tests	19.3	0.0041	29.3	1.8	24.3	0.91

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

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
	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded
Basic Person Test	32.3	0.011	20.3	1.5	26.3	0.74
Element Collection Test	14.3	0.010	6.0	1.6	10.2	0.80
Inheritance Test	29.2	0.0093	23.9	1.1	26.6	0.57
Indexing Test	55.3	0.017	27.1	2.1	41.2	1.1
Graph (Binary Tree) Test	6.8	failed	14.1	failed	10.4	failed
Multithreading Test	52.9	failed	28.4	failed	40.6	failed
All Tests	31.8	0.012	20.0	1.6	25.9	0.79

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
	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded	EclipseLink HSQLDB embedded	DataNucleus DB4O embedded
Basic Person Test	41.4	35.1	41.4	35.4	41.4	35.2
Element Collection Test	46.9	29.5	46.9	29.9	46.9	29.7
Inheritance Test	41.4	33.4	41.4	33.5	41.4	33.4
Indexing Test	48.4	41.0	49.2	41.9	48.8	41.5
Graph (Binary Tree) Test	28.5	failed	21.4	failed	25.0	failed
Multithreading Test	51.9	failed	10.3	failed	31.1	failed
All Tests	43.1	34.8	35.1	35.2	39.1	35.0

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

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.