Comparison of DataNucleus with SQLite embedded vs EclipseLink with PostgreSQL server

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 PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server
Basic Person Test		7.8		11.7		9.8
Element Collection Test		9.4		9.1		9.2
Inheritance Test		6.2		12.4		9.3
Indexing Test		10.7		12.7		11.7
Graph (Binary Tree) Test		7.8		7.9		7.8
Multithreading Test		10.9		0.0000		5.4
All Tests		8.8		9.0		8.9

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server
Basic Person Test	0.43	2.2		10.8	0.43	6.5
Element Collection Test		0.52		0.47		0.50
Inheritance Test		2.0		9.6		5.8
Indexing Test		1.7		10.9		6.3
Graph (Binary Tree) Test		0.22		0.48		0.35
Multithreading Test		3.2		16.7		10.0
All Tests	0.43	1.6		8.2	0.43	4.9

The results above show that in general EclipseLink with PostgreSQL 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 PostgreSQL database server (4.9) reveals that in these tests, EclipseLink with PostgreSQL server is 11.4 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 PostgreSQL database server (2.2) reveals that in that case, EclipseLink with PostgreSQL server is 5.1 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 PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server
Basic Person Test	failed	1.1		3.7	failed	2.4
Element Collection Test		1.1		0.51		0.80
Inheritance Test		0.99		4.5		2.8
Indexing Test		0.76		3.5		2.1
Multithreading Test		4.2		6.9		5.5
All Tests	failed	1.6		3.8	failed	2.7

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 PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server
Basic Person Test	0.025	1.8		3.7	0.025	2.7
Element Collection Test		2.0		1.0		1.5
Inheritance Test		1.5		5.1		3.3
Indexing Test		3.4		5.0		4.2
Graph (Binary Tree) Test		0.63		0.44		0.54
Multithreading Test		4.5		3.4		3.9
All Tests	0.025	2.3		3.1	0.025	2.7

The results above show that in general EclipseLink with PostgreSQL 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 PostgreSQL database server (2.7) reveals that in these tests, EclipseLink with PostgreSQL server is 108 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 PostgreSQL database server (1.8) reveals that in that case, EclipseLink with PostgreSQL server is 72.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
	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server
Basic Person Test	0.17	14.1		19.7	0.17	16.9
Element Collection Test		4.8		0.55		2.7
Inheritance Test		16.8		15.6		16.2
Indexing Test		20.7		14.6		17.7
Graph (Binary Tree) Test		6.0		8.0		7.0
Multithreading Test		23.4		0.0000		11.7
All Tests	0.17	14.3		9.7	0.17	12.0

The results above show that in general EclipseLink with PostgreSQL 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 PostgreSQL database server (12.0) reveals that in these tests, EclipseLink with PostgreSQL server is 70.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 PostgreSQL database server (14.1) reveals that in that case, EclipseLink with PostgreSQL server is 82.9 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
	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server	DataNucleus SQLite embedded	EclipseLink PostgreSQL server
Basic Person Test	0.21	5.4		9.9	0.21	7.7
Element Collection Test		3.5		2.3		2.9
Inheritance Test		5.5		9.4		7.5
Indexing Test		7.4		9.3		8.4
Graph (Binary Tree) Test		3.7		4.2		3.9
Multithreading Test		9.2		5.4		7.3
All Tests	0.21	5.9		6.9	0.21	6.4

The results above show that in general EclipseLink with PostgreSQL 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 PostgreSQL database server (6.4) reveals that in these tests, EclipseLink with PostgreSQL server is 30.5 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 PostgreSQL database server (5.4) reveals that in that case, EclipseLink with PostgreSQL server is 25.7 times faster than DataNucleus with SQLite embedded.

JPA Performance Benchmark (JPAB)