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

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
	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded
Basic Person Test	failed	13.2	failed	13.5	failed	13.3
Element Collection Test	0.0007	6.4	failed	8.9	0.0007	7.7
Inheritance Test	failed	12.2	failed	12.7	failed	12.4
Indexing Test	failed	8.1	failed	16.5	failed	12.3
Graph (Binary Tree) Test	failed	10.6	failed	20.9	failed	15.8
Multithreading Test	failed	13.3	failed	9.9	failed	11.6
All Tests	0.0007	10.6	failed	13.7	0.0007	12.2

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
	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded
Basic Person Test	1.2	4.7	failed	1.4	1.2	3.1
Element Collection Test	0.29	5.0	failed	2.4	0.29	3.7
Inheritance Test	0.69	3.8	failed	1.6	0.69	2.7
Indexing Test	0.0008	0.0041	failed	1.8	0.0008	0.91
Multithreading Test	failed	1.2	failed	0.79	failed	1.0
All Tests	0.55	3.0	failed	1.6	0.55	2.3

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
	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded
Basic Person Test	failed	10.0	failed	3.9	failed	6.9
Element Collection Test	0.0016	7.6	failed	3.9	0.0016	5.8
Inheritance Test	failed	9.4	failed	4.4	failed	6.9
Indexing Test	failed	10.6	failed	5.9	failed	8.2
Graph (Binary Tree) Test	failed	5.9	failed	3.7	failed	4.8
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.0016	8.7	failed	4.4	0.0016	6.5

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

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

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

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

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

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

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
	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded	EclipseLink SQLite embedded	DataNucleus H2 embedded
Basic Person Test	0.66	10.3	0.90	5.6	0.74	7.9
Element Collection Test	0.070	6.1	0.65	3.9	0.17	5.0
Inheritance Test	0.38	9.0	0.82	4.9	0.53	6.9
Indexing Test	0.058	10.1	1.6	7.6	0.58	8.9
Graph (Binary Tree) Test	0.24	7.8	0.91	8.7	0.57	8.3
Multithreading Test	0.10	16.5	2.1	5.9	1.1	11.2
All Tests	0.22	9.6	1.2	6.0	0.52	7.8

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)