Comparison of DataNucleus with Derby 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 Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded
Basic Person Test	4.6	0.074	2.8	0.90	3.7	0.49
Element Collection Test	2.4	0.061	1.6	0.65	2.0	0.36
Inheritance Test	4.6	0.083	2.7	0.82	3.7	0.45
Indexing Test	7.6	0.11	4.8	1.6	6.2	0.87
Graph (Binary Tree) Test	1.6	0.24	1.4	0.91	1.5	0.57
Multithreading Test	8.6	0.10	3.3	2.1	5.9	1.1
All Tests	4.9	0.11	2.8	1.2	3.8	0.64

The results above show that in general DataNucleus with Derby embedded is much more efficient than EclipseLink with SQLite embedded in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.64) to the normalized speed of DataNucleus with Derby embedded database (3.8) reveals that in these tests, DataNucleus with Derby embedded is 5.9 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.10) to the normalized speed of DataNucleus with Derby embedded database (8.6) reveals that in that case, DataNucleus with Derby embedded is 86.0 times faster than EclipseLink with SQLite embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded
Basic Person Test	6.8	failed	14.9	failed	10.9	failed
Element Collection Test	5.4	0.0007	7.6	failed	6.5	0.0007
Inheritance Test	8.8	failed	14.8	failed	11.8	failed
Indexing Test	9.2	failed	14.1	failed	11.6	failed
Graph (Binary Tree) Test	9.9	failed	15.8	failed	12.9	failed
Multithreading Test	11.9	failed	11.5	failed	11.7	failed
All Tests	8.7	0.0007	13.1	failed	10.9	0.0007

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 Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded
Basic Person Test	39.1	1.2	7.5	failed	23.3	1.2
Element Collection Test	46.0	0.29	6.7	failed	26.3	0.29
Inheritance Test	7.7	0.69	3.8	failed	5.7	0.69
Indexing Test	0.053	0.0008	8.0	failed	4.0	0.0008
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	23.2	0.55	6.5	failed	14.8	0.55

DataNucleus with Derby embedded has failed in 2 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 Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded
Basic Person Test	4.0	failed	3.8	failed	3.9	failed
Element Collection Test	3.7	0.0016	4.5	failed	4.1	0.0016
Inheritance Test	4.4	failed	4.8	failed	4.6	failed
Indexing Test	5.2	failed	4.2	failed	4.7	failed
Graph (Binary Tree) Test	2.7	failed	1.5	failed	2.1	failed
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	4.0	0.0016	3.7	failed	3.9	0.0016

DataNucleus with Derby embedded has failed in 2 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 Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded
Basic Person Test	3.5	failed	1.3	failed	2.4	failed
Element Collection Test	1.9	0.0006	1.6	failed	1.7	0.0006
Inheritance Test	2.4	failed	1.3	failed	1.9	failed
Indexing Test	6.6	failed	1.9	failed	4.3	failed
Graph (Binary Tree) Test	0.81	failed	0.93	failed	0.87	failed
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	3.0	0.0006	1.4	failed	2.2	0.0006

DataNucleus with Derby embedded has failed in 2 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 Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded
Basic Person Test	53.3	79.4	53.3	79.4	53.3	79.4
Element Collection Test	42.6	74.5	42.6	74.5	42.6	74.5
Inheritance Test	48.1	75.0	48.1	75.0	48.1	75.0
Indexing Test	62.3	92.9	63.3	94.5	62.8	93.7
Graph (Binary Tree) Test	13.6	60.6	10.2	48.4	11.9	54.5
Multithreading Test	52.0	100	8.0	100	30.0	100
All Tests	45.3	80.4	37.6	78.6	41.5	79.5

The results above show that in general EclipseLink with SQLite embedded is more efficient than DataNucleus with Derby embedded in using disk space.

A huge gap has been detected when using multithreading with large transaction size. Comparing the normalized score of DataNucleus with Derby embedded database (8.0) to the normalized score of EclipseLink with SQLite embedded database (100) reveals that in that case, EclipseLink with SQLite embedded is 12.5 times more efficient than DataNucleus with Derby embedded.

Comparison of JPA/Database speed - the averages (normalized score, higher is better)

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded	DataNucleus Derby embedded	EclipseLink SQLite embedded
Basic Person Test	11.6	0.66	6.1	0.90	8.8	0.74
Element Collection Test	11.9	0.070	4.4	0.65	8.1	0.17
Inheritance Test	5.6	0.38	5.5	0.82	5.5	0.53
Indexing Test	5.7	0.058	6.6	1.6	6.2	0.58
Graph (Binary Tree) Test	3.7	0.24	4.9	0.91	4.3	0.57
Multithreading Test	10.3	0.10	7.4	2.1	8.8	1.1
All Tests	8.0	0.22	5.7	1.2	6.9	0.52

The results above show that in general DataNucleus with Derby embedded is much more efficient than EclipseLink with SQLite embedded in performing JPA database operations. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.52) to the normalized speed of DataNucleus with Derby embedded database (6.9) reveals that in these tests, DataNucleus with Derby embedded is 13.3 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.070) to the normalized speed of DataNucleus with Derby embedded database (11.9) reveals that in that case, DataNucleus with Derby embedded is 170 times faster than EclipseLink with SQLite embedded.

JPA Performance Benchmark (JPAB)