Comparison of EclipseLink with Derby server vs DataNucleus 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
	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded
Basic Person Test	9.2		8.9		9.0
Element Collection Test	8.0		6.8		7.4
Inheritance Test	5.6		9.3		7.4
Indexing Test	9.6		11.0		10.3
Graph (Binary Tree) Test	8.1		7.4		7.8
Multithreading Test	10.8		0.0000		5.4
All Tests	8.6		7.2		7.9

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded
Basic Person Test	1.8	0.43	7.6		4.7	0.43
Element Collection Test	0.86		0.58		0.72
Inheritance Test	1.8		6.6		4.2
Indexing Test	1.7		7.7		4.7
Graph (Binary Tree) Test	0.12		0.26		0.19
Multithreading Test	2.5		12.5		7.5
All Tests	1.5	0.43	5.9		3.7	0.43

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

A large 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 database server (1.8) reveals that in that case, EclipseLink with Derby server is 4.2 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
	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded
Basic Person Test	0.46	failed	2.4		1.4	failed
Element Collection Test	0.92		1.1		1.0
Inheritance Test	0.42		2.4		1.4
Indexing Test	1.3		3.3		2.3
Multithreading Test	2.4		4.3		3.4
All Tests	1.1	failed	2.7		1.9	failed

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
	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded
Basic Person Test	1.7	0.025	4.1		2.9	0.025
Element Collection Test	2.6		1.2		1.9
Inheritance Test	1.6		5.2		3.4
Indexing Test	6.0		5.5		5.8
Graph (Binary Tree) Test	0.67		0.41		0.54
Multithreading Test	1.7		4.6		3.2
All Tests	2.4	0.025	3.5		3.0	0.025

The results above show that in general EclipseLink with Derby server 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 database server (3.0) reveals that in these tests, EclipseLink with Derby server is 120 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 database server (1.7) reveals that in that case, EclipseLink with Derby server is 68.0 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
	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded
Basic Person Test	10.6	0.17	7.4		9.0	0.17
Element Collection Test	6.0		0.67		3.3
Inheritance Test	12.6		14.1		13.3
Indexing Test	18.7		10.1		14.4
Graph (Binary Tree) Test	5.8		9.9		7.9
Multithreading Test	6.6		0.0000		3.3
All Tests	10.1	0.17	7.0		8.5	0.17

The results above show that in general EclipseLink with Derby server 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 database server (8.5) reveals that in these tests, EclipseLink with Derby server is 50.0 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 database server (10.6) reveals that in that case, EclipseLink with Derby server is 62.4 times faster than DataNucleus with SQLite embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded	EclipseLink Derby server	DataNucleus SQLite embedded
Basic Person Test	4.8	0.21	6.1		5.4	0.21
Element Collection Test	3.7		2.1		2.9
Inheritance Test	4.4		7.5		6.0
Indexing Test	7.5		7.5		7.5
Graph (Binary Tree) Test	3.7		4.5		4.1
Multithreading Test	4.8		4.3		4.6
All Tests	4.8	0.21	5.4		5.1	0.21

The results above show that in general EclipseLink with Derby server 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 database server (5.1) reveals that in these tests, EclipseLink with Derby server is 24.3 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 database server (4.8) reveals that in that case, EclipseLink with Derby server is 22.9 times faster than DataNucleus with SQLite embedded.

JPA Performance Benchmark (JPAB)