Comparison of EclipseLink with HSQLDB embedded 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 HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded
Basic Person Test	14.5		14.1		14.3
Element Collection Test	13.2		10.2		11.7
Inheritance Test	9.9		15.0		12.4
Indexing Test	15.3		15.6		15.4
Graph (Binary Tree) Test	8.0		8.1		8.0
Multithreading Test	11.8		0.0000		5.9
All Tests	12.1		10.5		11.3

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded
Basic Person Test	36.1	0.43	34.4		35.3	0.43
Element Collection Test	17.9		31.9		24.9
Inheritance Test	14.0		38.8		26.4
Indexing Test	21.9		52.5		37.2
Graph (Binary Tree) Test	5.7		8.4		7.0
Multithreading Test	26.3		28.0		27.2
All Tests	20.3	0.43	32.4		26.3	0.43

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (26.3) reveals that in these tests, EclipseLink with HSQLDB embedded is 61.2 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 HSQLDB embedded database (36.1) reveals that in that case, EclipseLink with HSQLDB embedded is 84.0 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 HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded
Basic Person Test	0.68	failed	3.4		2.0	failed
Element Collection Test	1.5		5.5		3.5
Inheritance Test	0.58		4.1		2.3
Indexing Test	22.8		34.0		28.4
Multithreading Test	0.47		1.3		0.88
All Tests	5.2	failed	9.7		7.4	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 HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded
Basic Person Test	13.2	0.025	10.4		11.8	0.025
Element Collection Test	24.3		10.5		17.4
Inheritance Test	15.3		13.3		14.3
Indexing Test	41.0		12.3		26.7
Graph (Binary Tree) Test	7.7		4.6		6.1
Multithreading Test	7.2		5.9		6.6
All Tests	18.1	0.025	9.5		13.8	0.025

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (13.8) reveals that in these tests, EclipseLink with HSQLDB embedded is 552 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 HSQLDB embedded database (13.2) reveals that in that case, EclipseLink with HSQLDB embedded is 528 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 HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded
Basic Person Test	59.9	0.17	37.5		48.7	0.17
Element Collection Test	22.7		3.4		13.0
Inheritance Test	59.4		22.6		41.0
Indexing Test	93.6		18.8		56.2
Graph (Binary Tree) Test	18.5		26.2		22.4
Multithreading Test	17.9		100		58.9
All Tests	45.3	0.17	34.7		40.0	0.17

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (40.0) reveals that in these tests, EclipseLink with HSQLDB embedded is 235 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 HSQLDB embedded database (59.9) reveals that in that case, EclipseLink with HSQLDB embedded is 352 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
	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded
Basic Person Test	98.1		98.1		98.1
Element Collection Test	49.4		49.4		49.4
Inheritance Test	100		98.4		99.2
Indexing Test	98.3		98.3		98.3
Graph (Binary Tree) Test	95.3		95.3		95.3
Multithreading Test	98.1		98.1		98.1
All Tests	89.9		89.6		89.7

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded	EclipseLink HSQLDB embedded	DataNucleus SQLite embedded
Basic Person Test	24.9	0.21	20.0		22.4	0.21
Element Collection Test	15.9		12.3		14.1
Inheritance Test	19.8		18.8		19.3
Indexing Test	38.9		26.7		32.8
Graph (Binary Tree) Test	10.0		11.8		10.9
Multithreading Test	12.7		27.0		19.9
All Tests	20.7	0.21	19.7		20.2	0.21

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (20.2) reveals that in these tests, EclipseLink with HSQLDB embedded is 96.2 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 HSQLDB embedded database (24.9) reveals that in that case, EclipseLink with HSQLDB embedded is 119 times faster than DataNucleus with SQLite embedded.

JPA Performance Benchmark (JPAB)