• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus with DB4O embedded vs EclipseLink with SQLite 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 SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded
Basic Person Test	0.059	0.074	1.3	0.90	0.69	0.49
Element Collection Test	0.045	0.061	1.0	0.65	0.52	0.36
Inheritance Test	0.051	0.083	0.85	0.82	0.45	0.45
Indexing Test	0.080	0.11	2.3	1.6	1.2	0.87
Graph (Binary Tree) Test	failed	0.24	failed	0.91	failed	0.57
Multithreading Test	failed	0.10	failed	2.1	failed	1.1
All Tests	0.059	0.11	1.4	1.2	0.71	0.64

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

The results above show that in general DataNucleus with DB4O embedded is slightly more efficient than EclipseLink with SQLite embedded in persisting JPA entity objects to the database.

Speed comparison of JPA database retrieval operations (normalized score, higher is better)

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded
Basic Person Test	0.0047	failed	1.8	failed	0.90	failed
Element Collection Test	0.0038	0.0007	1.5	failed	0.77	0.0007
Inheritance Test	0.0035	failed	2.2	failed	1.1	failed
Indexing Test	0.0043	failed	1.8	failed	0.89	failed
Graph (Binary Tree) Test	failed	failed	failed	failed	failed	failed
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.0041	0.0007	1.8	failed	0.91	0.0007

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

Speed comparison of JPA database query operations (normalized score, higher is better)

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded
Basic Person Test	failed	1.2	failed	failed	failed	1.2
Element Collection Test	failed	0.29	failed	failed	failed	0.29
Inheritance Test	failed	0.69	failed	failed	failed	0.69
Indexing Test	failed	0.0008	failed	failed	failed	0.0008
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	failed	0.55	failed	failed	failed	0.55

DataNucleus with DB4O embedded has failed in 10 tests (see exceptions). EclipseLink with SQLite embedded has failed in 6 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 SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded
Basic Person Test	0.012	failed	0.76	failed	0.39	failed
Element Collection Test	0.012	0.0016	1.1	failed	0.53	0.0016
Inheritance Test	0.011	failed	0.81	failed	0.41	failed
Indexing Test	0.011	failed	1.3	failed	0.64	failed
Graph (Binary Tree) Test	failed	failed	failed	failed	failed	failed
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.012	0.0016	0.97	failed	0.49	0.0016

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

Speed comparison of JPA database removal operations (normalized score, higher is better)

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded
Basic Person Test	0.011	failed	1.5	failed	0.74	failed
Element Collection Test	0.010	0.0006	1.6	failed	0.80	0.0006
Inheritance Test	0.0093	failed	1.1	failed	0.57	failed
Indexing Test	0.017	failed	2.1	failed	1.1	failed
Graph (Binary Tree) Test	failed	failed	failed	failed	failed	failed
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.012	0.0006	1.6	failed	0.79	0.0006

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

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded
Basic Person Test	35.1	79.4	35.4	79.4	35.2	79.4
Element Collection Test	29.5	74.5	29.9	74.5	29.7	74.5
Inheritance Test	33.4	75.0	33.5	75.0	33.4	75.0
Indexing Test	41.0	92.9	41.9	94.5	41.5	93.7
Graph (Binary Tree) Test	failed	60.6	failed	48.4	failed	54.5
Multithreading Test	failed	100	failed	100	failed	100
All Tests	34.8	80.4	35.2	78.6	35.0	79.5

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

The results above show that in general EclipseLink with SQLite embedded is more efficient than DataNucleus with DB4O embedded in using disk space. Comparing the normalized score of DataNucleus with DB4O embedded database (35.0) to the normalized score of EclipseLink with SQLite embedded database (79.5) reveals that in these tests, EclipseLink with SQLite embedded is 2.3 times more efficient than DataNucleus with DB4O embedded.

A large gap has been detected when using JPA element collections with small transaction size. Comparing the normalized score of DataNucleus with DB4O embedded database (29.5) to the normalized score of EclipseLink with SQLite embedded database (74.5) reveals that in that case, EclipseLink with SQLite embedded is 2.5 times more efficient than DataNucleus with DB4O embedded.

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 SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded	DataNucleus DB4O embedded	EclipseLink SQLite embedded
Basic Person Test	0.022	0.66	1.3	0.90	0.68	0.74
Element Collection Test	0.018	0.070	1.3	0.65	0.66	0.17
Inheritance Test	0.019	0.38	1.2	0.82	0.63	0.53
Indexing Test	0.028	0.058	1.9	1.6	0.94	0.58
Graph (Binary Tree) Test	failed	0.24	failed	0.91	failed	0.57
Multithreading Test	failed	0.10	failed	2.1	failed	1.1
All Tests	0.022	0.22	1.4	1.2	0.73	0.52

The results above show that in general DataNucleus with DB4O embedded is more efficient than EclipseLink with SQLite embedded in performing JPA database operations.

A large performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.65) to the normalized speed of DataNucleus with DB4O embedded database (1.3) reveals that in that case, DataNucleus with DB4O embedded is 2.0 times faster than EclipseLink with SQLite embedded.

On the other hand, DataNucleus with DB4O embedded is slower, for instance, 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 SQLite embedded database (0.66) reveals that in that case, DataNucleus with DB4O embedded is 30.0 times slower than EclipseLink with SQLite 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.