Comparison of DataNucleus with SQLite embedded vs EclipseLink with Derby 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 SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded
Basic Person Test		11.5		9.1		10.3
Element Collection Test		7.3		5.5		6.4
Inheritance Test		6.6		7.5		7.0
Indexing Test		10.9		12.7		11.8
Graph (Binary Tree) Test		3.6		2.9		3.3
Multithreading Test		10.4		0.0000		5.2
All Tests		8.4		6.3		7.3

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded
Basic Person Test	0.43	12.3		29.3	0.43	20.8
Element Collection Test		7.5		11.7		9.6
Inheritance Test		6.2		29.0		17.6
Indexing Test		5.4		31.9		18.7
Graph (Binary Tree) Test		0.93		3.3		2.1
Multithreading Test		15.2		32.4		23.8
All Tests	0.43	7.9		22.9	0.43	15.4

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

A huge performance gap has been detected when using simple basic entities with small retrieval size. Comparing the normalized speed of DataNucleus with SQLite embedded database (0.43) to the normalized speed of EclipseLink with Derby embedded database (12.3) reveals that in that case, EclipseLink with Derby embedded is 28.6 times faster than DataNucleus with SQLite embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded
Basic Person Test	failed	1.4		5.9	failed	3.6
Element Collection Test		2.9		6.0		4.5
Inheritance Test		0.97		7.1		4.0
Indexing Test		13.8		18.5		16.1
Multithreading Test		4.6		10.4		7.5
All Tests	failed	4.7		9.6	failed	7.2

DataNucleus with SQLite embedded has failed in 1 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded
Basic Person Test	0.025	3.3		6.2	0.025	4.8
Element Collection Test		10.0		5.5		7.7
Inheritance Test		3.9		7.6		5.8
Indexing Test		10.3		8.3		9.3
Graph (Binary Tree) Test		1.7		1.7		1.7
Multithreading Test		5.2		5.5		5.3
All Tests	0.025	5.8		5.8	0.025	5.8

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

A huge performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with SQLite embedded database (0.025) to the normalized speed of EclipseLink with Derby embedded database (3.3) reveals that in that case, EclipseLink with Derby embedded is 132 times faster than DataNucleus with SQLite embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded
Basic Person Test	0.17	12.9		12.2	0.17	12.5
Element Collection Test		12.6		1.1		6.8
Inheritance Test		14.1		7.6		10.9
Indexing Test		20.6		4.4		12.5
Graph (Binary Tree) Test		5.0		7.4		6.2
Multithreading Test		4.8		0.0000		2.4
All Tests	0.17	11.6		5.5	0.17	8.6

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

A huge performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with SQLite embedded database (0.17) to the normalized speed of EclipseLink with Derby embedded database (12.9) reveals that in that case, EclipseLink with Derby embedded is 75.9 times faster than DataNucleus with SQLite embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded
Basic Person Test		14.6		14.6		14.6
Element Collection Test		15.8		15.8		15.8
Inheritance Test		15.9		16.4		16.2
Indexing Test		15.0		15.0		15.0
Graph (Binary Tree) Test		5.7		5.7		5.7
Multithreading Test		12.1		12.1		12.1
All Tests		13.2		13.3		13.2

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded	DataNucleus SQLite embedded	EclipseLink Derby embedded
Basic Person Test	0.21	8.3		12.5	0.21	10.4
Element Collection Test		8.1		6.0		7.0
Inheritance Test		6.4		11.7		9.0
Indexing Test		12.2		15.2		13.7
Graph (Binary Tree) Test		2.8		3.8		3.3
Multithreading Test		8.0		9.7		8.8
All Tests	0.21	7.8		10.0	0.21	8.9

The results above show that in general EclipseLink with Derby embedded is much more efficient than DataNucleus with SQLite embedded in performing JPA database operations. Comparing the normalized speed of DataNucleus with SQLite embedded database (0.21) to the normalized speed of EclipseLink with Derby embedded database (8.9) reveals that in these tests, EclipseLink with Derby embedded is 42.4 times faster than DataNucleus with SQLite 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 SQLite embedded database (0.21) to the normalized speed of EclipseLink with Derby embedded database (8.3) reveals that in that case, EclipseLink with Derby embedded is 39.5 times faster than DataNucleus with SQLite embedded.

JPA Performance Benchmark (JPAB)