Comparison of DataNucleus with SQLite embedded vs EclipseLink with H2 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 H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded
Basic Person Test		15.4		12.9		14.2
Element Collection Test		14.1		8.4		11.3
Inheritance Test		8.4		9.7		9.1
Indexing Test		15.5		14.2		14.9
Graph (Binary Tree) Test		8.5		7.1		7.8
Multithreading Test		12.3		0.0000		6.1
All Tests		12.4		8.7		10.5

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus SQLite embedded	EclipseLink H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded
Basic Person Test	0.43	18.6		30.2	0.43	24.4
Element Collection Test		16.3		21.5		18.9
Inheritance Test		19.7		27.1		23.4
Indexing Test		17.9		29.1		23.5
Graph (Binary Tree) Test		5.9		18.3		12.1
Multithreading Test		26.9		39.9		33.4
All Tests	0.43	17.6		27.7	0.43	22.6

The results above show that in general EclipseLink with H2 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 H2 embedded database (22.6) reveals that in these tests, EclipseLink with H2 embedded is 52.6 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 H2 embedded database (18.6) reveals that in that case, EclipseLink with H2 embedded is 43.3 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 H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded
Basic Person Test	failed	3.5		12.2	failed	7.8
Element Collection Test		7.6		10.1		8.9
Inheritance Test		2.2		12.3		7.3
Indexing Test		11.5		21.6		16.6
Multithreading Test		3.2		12.0		7.6
All Tests	failed	5.6		13.6	failed	9.6

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 H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded
Basic Person Test	0.025	21.0		9.3	0.025	15.1
Element Collection Test		26.7		12.3		19.5
Inheritance Test		15.6		14.0		14.8
Indexing Test		53.2		12.4		32.8
Graph (Binary Tree) Test		11.4		6.1		8.7
Multithreading Test		14.9		6.6		10.7
All Tests	0.025	23.8		10.1	0.025	17.0

The results above show that in general EclipseLink with H2 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 H2 embedded database (17.0) reveals that in these tests, EclipseLink with H2 embedded is 680 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 H2 embedded database (21.0) reveals that in that case, EclipseLink with H2 embedded is 840 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 H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded
Basic Person Test	0.17	43.5		29.0	0.17	36.2
Element Collection Test		31.5		3.9		17.7
Inheritance Test		49.9		20.7		35.3
Indexing Test		83.8		15.9		49.9
Graph (Binary Tree) Test		35.3		39.8		37.6
Multithreading Test		28.0		0.0000		14.0
All Tests	0.17	45.3		18.2	0.17	31.8

The results above show that in general EclipseLink with H2 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 H2 embedded database (31.8) reveals that in these tests, EclipseLink with H2 embedded is 187 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 H2 embedded database (43.5) reveals that in that case, EclipseLink with H2 embedded is 256 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 H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded
Basic Person Test		68.1		74.9		71.5
Element Collection Test		74.0		74.9		74.4
Inheritance Test		74.6		82.8		78.7
Indexing Test		68.4		75.8		72.1
Graph (Binary Tree) Test		87.0		83.5		85.3
Multithreading Test		77.1		75.5		76.3
All Tests		74.9		77.9		76.4

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 H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded	DataNucleus SQLite embedded	EclipseLink H2 embedded
Basic Person Test	0.21	20.4		18.7	0.21	19.6
Element Collection Test		19.2		11.2		15.2
Inheritance Test		19.2		16.8		18.0
Indexing Test		36.4		18.7		27.5
Graph (Binary Tree) Test		15.3		17.8		16.5
Multithreading Test		17.0		11.7		14.4
All Tests	0.21	21.5		15.7	0.21	18.6

The results above show that in general EclipseLink with H2 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 H2 embedded database (18.6) reveals that in these tests, EclipseLink with H2 embedded is 88.6 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 H2 embedded database (20.4) reveals that in that case, EclipseLink with H2 embedded is 97.1 times faster than DataNucleus with SQLite embedded.

JPA Performance Benchmark (JPAB)