Comparison of DataNucleus with H2 embedded vs EclipseLink 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
	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded
Basic Person Test	19.2	0.074	8.0	0.90	13.6	0.49
Element Collection Test	6.6	0.061	2.8	0.65	4.7	0.36
Inheritance Test	15.6	0.083	4.4	0.82	10.0	0.45
Indexing Test	24.4	0.11	11.8	1.6	18.1	0.87
Graph (Binary Tree) Test	9.2	0.24	6.2	0.91	7.7	0.57
Multithreading Test	34.9	0.10	7.1	2.1	21.0	1.1
All Tests	18.3	0.11	6.7	1.2	12.5	0.64

The results above show that in general DataNucleus with H2 embedded is much more efficient than EclipseLink with SQLite embedded in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.64) to the normalized speed of DataNucleus with H2 embedded database (12.5) reveals that in these tests, DataNucleus with H2 embedded is 19.5 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.10) to the normalized speed of DataNucleus with H2 embedded database (34.9) reveals that in that case, DataNucleus with H2 embedded is 349 times faster than EclipseLink with SQLite embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded
Basic Person Test	13.2	failed	13.5	failed	13.3	failed
Element Collection Test	6.4	0.0007	8.9	failed	7.7	0.0007
Inheritance Test	12.2	failed	12.7	failed	12.4	failed
Indexing Test	8.1	failed	16.5	failed	12.3	failed
Graph (Binary Tree) Test	10.6	failed	20.9	failed	15.8	failed
Multithreading Test	13.3	failed	9.9	failed	11.6	failed
All Tests	10.6	0.0007	13.7	failed	12.2	0.0007

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded
Basic Person Test	4.7	1.2	1.4	failed	3.1	1.2
Element Collection Test	5.0	0.29	2.4	failed	3.7	0.29
Inheritance Test	3.8	0.69	1.6	failed	2.7	0.69
Indexing Test	0.0041	0.0008	1.8	failed	0.91	0.0008
Multithreading Test	1.2	failed	0.79	failed	1.0	failed
All Tests	3.0	0.55	1.6	failed	2.3	0.55

EclipseLink with SQLite embedded has failed in 6 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded
Basic Person Test	10.0	failed	3.9	failed	6.9	failed
Element Collection Test	7.6	0.0016	3.9	failed	5.8	0.0016
Inheritance Test	9.4	failed	4.4	failed	6.9	failed
Indexing Test	10.6	failed	5.9	failed	8.2	failed
Graph (Binary Tree) Test	5.9	failed	3.7	failed	4.8	failed
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	8.7	0.0016	4.4	failed	6.5	0.0016

DataNucleus with H2 embedded has failed in 2 tests (see exceptions). EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded
Basic Person Test	4.2	failed	1.3	failed	2.8	failed
Element Collection Test	4.9	0.0006	1.6	failed	3.2	0.0006
Inheritance Test	4.0	failed	1.3	failed	2.7	failed
Indexing Test	7.5	failed	1.9	failed	4.7	failed
Graph (Binary Tree) Test	5.6	failed	4.1	failed	4.8	failed
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	5.2	0.0006	2.0	failed	3.6	0.0006

DataNucleus with H2 embedded has failed in 2 tests (see exceptions). EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded
Basic Person Test	27.0	79.4	27.0	79.4	27.0	79.4
Element Collection Test	22.4	74.5	22.4	74.5	22.4	74.5
Inheritance Test	27.0	75.0	27.0	75.0	27.0	75.0
Indexing Test	31.6	92.9	32.1	94.5	31.9	93.7
Graph (Binary Tree) Test	20.0	60.6	15.0	48.4	17.5	54.5
Multithreading Test	33.9	100	9.2	100	21.5	100
All Tests	27.0	80.4	22.1	78.6	24.6	79.5

The results above show that in general EclipseLink with SQLite embedded is much more efficient than DataNucleus with H2 embedded in using disk space. Comparing the normalized score of DataNucleus with H2 embedded database (24.6) to the normalized score of EclipseLink with SQLite embedded database (79.5) reveals that in these tests, EclipseLink with SQLite embedded is 3.2 times more efficient than DataNucleus with H2 embedded.

A huge gap has been detected when using multithreading with large transaction size. Comparing the normalized score of DataNucleus with H2 embedded database (9.2) to the normalized score of EclipseLink with SQLite embedded database (100) reveals that in that case, EclipseLink with SQLite embedded is 10.9 times more efficient than DataNucleus with H2 embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded
Basic Person Test	10.3	0.66	5.6	0.90	7.9	0.74
Element Collection Test	6.1	0.070	3.9	0.65	5.0	0.17
Inheritance Test	9.0	0.38	4.9	0.82	6.9	0.53
Indexing Test	10.1	0.058	7.6	1.6	8.9	0.58
Graph (Binary Tree) Test	7.8	0.24	8.7	0.91	8.3	0.57
Multithreading Test	16.5	0.10	5.9	2.1	11.2	1.1
All Tests	9.6	0.22	6.0	1.2	7.8	0.52

The results above show that in general DataNucleus with H2 embedded is much more efficient than EclipseLink with SQLite embedded in performing JPA database operations. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.52) to the normalized speed of DataNucleus with H2 embedded database (7.8) reveals that in these tests, DataNucleus with H2 embedded is 15.0 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.058) to the normalized speed of DataNucleus with H2 embedded database (10.1) reveals that in that case, DataNucleus with H2 embedded is 174 times faster than EclipseLink with SQLite embedded.

JPA Performance Benchmark (JPAB)