• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with Derby 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 Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded
Basic Person Test	5.5	0.059	3.7	1.3	4.6	0.69
Element Collection Test	3.0	0.045	1.7	1.0	2.4	0.52
Inheritance Test	5.3	0.051	3.5	0.85	4.4	0.45
Indexing Test	6.9	0.080	4.6	2.3	5.8	1.2
Graph (Binary Tree) Test	2.0	failed	1.9	failed	1.9	failed
Multithreading Test	9.3	failed	4.1	failed	6.7	failed
All Tests	5.3	0.059	3.2	1.4	4.3	0.71

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

The results above show that in general EclipseLink with Derby 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 Derby embedded database (4.3) reveals that in these tests, EclipseLink with Derby embedded is 6.1 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 Derby embedded database (5.3) reveals that in that case, EclipseLink with Derby embedded is 104 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 Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded
Basic Person Test	16.4	0.0047	58.7	1.8	37.5	0.90
Element Collection Test	7.5	0.0038	13.3	1.5	10.4	0.77
Inheritance Test	17.1	0.0035	58.9	2.2	38.0	1.1
Indexing Test	14.2	0.0043	67.4	1.8	40.8	0.89
Graph (Binary Tree) Test	2.8	failed	5.7	failed	4.2	failed
Multithreading Test	28.0	failed	48.7	failed	38.4	failed
All Tests	14.3	0.0041	42.1	1.8	28.2	0.91

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

The results above show that in general EclipseLink with Derby 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 Derby embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 31.0 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 Derby embedded database (17.1) reveals that in that case, EclipseLink with Derby embedded is 4,886 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 Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded
Basic Person Test	53.4	failed	13.8	failed	33.6	failed
Element Collection Test	37.9	failed	4.4	failed	21.2	failed
Inheritance Test	37.4	failed	15.0	failed	26.2	failed
Indexing Test	7.6	failed	49.3	failed	28.4	failed
Multithreading Test	41.2	failed	6.1	failed	23.6	failed
All Tests	35.5	failed	17.7	failed	26.6	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 Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded
Basic Person Test	6.4	0.012	6.7	0.76	6.5	0.39
Element Collection Test	5.4	0.012	6.2	1.1	5.8	0.53
Inheritance Test	6.5	0.011	9.2	0.81	7.8	0.41
Indexing Test	7.3	0.011	11.1	1.3	9.2	0.64
Graph (Binary Tree) Test	2.8	failed	1.7	failed	2.2	failed
Multithreading Test	21.3	failed	5.0	failed	13.1	failed
All Tests	8.3	0.012	6.6	0.97	7.5	0.49

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

The results above show that in general EclipseLink with Derby 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 Derby embedded database (7.5) reveals that in these tests, EclipseLink with Derby embedded is 15.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 EclipseLink with Derby embedded database (7.3) reveals that in that case, EclipseLink with Derby embedded is 664 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 Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded
Basic Person Test	4.6	0.011	4.7	1.5	4.6	0.74
Element Collection Test	2.5	0.010	1.4	1.6	1.9	0.80
Inheritance Test	3.9	0.0093	4.5	1.1	4.2	0.57
Indexing Test	6.2	0.017	3.8	2.1	5.0	1.1
Graph (Binary Tree) Test	1.1	failed	1.0	failed	1.1	failed
Multithreading Test	6.2	failed	5.8	failed	6.0	failed
All Tests	4.1	0.012	3.5	1.6	3.8	0.79

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

The results above show that in general EclipseLink with Derby 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 Derby embedded database (3.8) reveals that in these tests, EclipseLink with Derby embedded is 4.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 Derby embedded database (3.9) reveals that in that case, EclipseLink with Derby embedded is 419 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 Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded
Basic Person Test	51.1	35.1	51.0	35.4	51.1	35.2
Element Collection Test	38.5	29.5	39.4	29.9	38.9	29.7
Inheritance Test	48.0	33.4	47.9	33.5	48.0	33.4
Indexing Test	51.6	41.0	52.3	41.9	52.0	41.5
Graph (Binary Tree) Test	13.4	failed	11.7	failed	12.6	failed
Multithreading Test	52.6	failed	8.4	failed	30.5	failed
All Tests	42.5	34.8	35.1	35.2	38.8	35.0

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

The results above show that in general EclipseLink with Derby 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 Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded	EclipseLink Derby embedded	DataNucleus DB4O embedded
Basic Person Test	17.3	0.022	17.5	1.3	17.4	0.68
Element Collection Test	11.3	0.018	5.4	1.3	8.3	0.66
Inheritance Test	14.0	0.019	18.2	1.2	16.1	0.63
Indexing Test	8.4	0.028	27.2	1.9	17.8	0.94
Graph (Binary Tree) Test	2.2	failed	2.6	failed	2.4	failed
Multithreading Test	21.2	failed	13.9	failed	17.6	failed
All Tests	12.7	0.022	14.5	1.4	13.6	0.73

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

A huge performance gap has been detected when using simple basic entities with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.022) to the normalized speed of EclipseLink with Derby embedded database (17.3) reveals that in that case, EclipseLink with Derby embedded is 786 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.