Comparison of EclipseLink with HSQLDB 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 HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded
Basic Person Test	27.1	19.2	17.2	8.0	22.2	13.6
Element Collection Test	17.2	6.6	8.2	2.8	12.7	4.7
Inheritance Test	26.7	15.6	11.9	4.4	19.3	10.0
Indexing Test	30.6	24.4	18.6	11.8	24.6	18.1
Graph (Binary Tree) Test	20.0	9.2	15.9	6.2	18.0	7.7
Multithreading Test	32.5	34.9	11.4	7.1	22.0	21.0
All Tests	25.7	18.3	13.9	6.7	19.8	12.5

The results above show that in general EclipseLink with HSQLDB embedded is more efficient than DataNucleus with H2 embedded in persisting JPA entity objects to the database.

A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with H2 embedded database (2.8) to the normalized speed of EclipseLink with HSQLDB embedded database (8.2) reveals that in that case, EclipseLink with HSQLDB embedded is 2.9 times faster than DataNucleus with H2 embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded
Basic Person Test	24.4	13.2	36.0	13.5	30.2	13.3
Element Collection Test	14.9	6.4	19.1	8.9	17.0	7.7
Inheritance Test	22.8	12.2	40.0	12.7	31.4	12.4
Indexing Test	20.7	8.1	38.7	16.5	29.7	12.3
Graph (Binary Tree) Test	8.7	10.6	14.2	20.9	11.4	15.8
Multithreading Test	24.2	13.3	28.0	9.9	26.1	11.6
All Tests	19.3	10.6	29.3	13.7	24.3	12.2

The results above show that in general EclipseLink with HSQLDB embedded is more efficient than DataNucleus with H2 embedded in retrieving JPA entity objects from the database.

A large performance gap has been detected when using class inheritance in the object model with large retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (12.7) to the normalized speed of EclipseLink with HSQLDB embedded database (40.0) reveals that in that case, EclipseLink with HSQLDB embedded is 3.1 times faster than DataNucleus with H2 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 H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded
Basic Person Test	2.9	4.7	0.88	1.4	1.9	3.1
Element Collection Test	3.2	5.0	1.4	2.4	2.3	3.7
Inheritance Test	2.6	3.8	1.1	1.6	1.9	2.7
Indexing Test	21.5	0.0041	33.3	1.8	27.4	0.91
Multithreading Test	1.1	1.2	0.52	0.79	0.82	1.0
All Tests	6.3	3.0	7.4	1.6	6.9	2.3

The results above show that in general EclipseLink with HSQLDB embedded is much more efficient than DataNucleus with H2 embedded in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with H2 embedded database (2.3) to the normalized speed of EclipseLink with HSQLDB embedded database (6.9) reveals that in these tests, EclipseLink with HSQLDB embedded is 3.0 times faster than DataNucleus with H2 embedded.

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (0.0041) to the normalized speed of EclipseLink with HSQLDB embedded database (21.5) reveals that in that case, EclipseLink with HSQLDB embedded is 5,244 times faster than DataNucleus with H2 embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded
Basic Person Test	17.9	10.0	7.0	3.9	12.5	6.9
Element Collection Test	14.6	7.6	8.3	3.9	11.4	5.8
Inheritance Test	16.2	9.4	9.7	4.4	13.0	6.9
Indexing Test	12.0	10.6	6.8	5.9	9.4	8.2
Graph (Binary Tree) Test	4.7	5.9	3.4	3.7	4.0	4.8
Multithreading Test	24.4	failed	4.4	failed	14.4	failed
All Tests	15.0	8.7	6.6	4.4	10.8	6.5

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

The results above show that in general EclipseLink with HSQLDB embedded is more efficient than DataNucleus with H2 embedded in updating JPA entity objects in the database.

A large performance gap has been detected when using class inheritance in the object model with large transaction size. Comparing the normalized speed of DataNucleus with H2 embedded database (4.4) to the normalized speed of EclipseLink with HSQLDB embedded database (9.7) reveals that in that case, EclipseLink with HSQLDB embedded is 2.2 times faster than DataNucleus with H2 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 H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded
Basic Person Test	32.3	4.2	20.3	1.3	26.3	2.8
Element Collection Test	14.3	4.9	6.0	1.6	10.2	3.2
Inheritance Test	29.2	4.0	23.9	1.3	26.6	2.7
Indexing Test	55.3	7.5	27.1	1.9	41.2	4.7
Graph (Binary Tree) Test	6.8	5.6	14.1	4.1	10.4	4.8
Multithreading Test	52.9	failed	28.4	failed	40.6	failed
All Tests	31.8	5.2	20.0	2.0	25.9	3.6

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

The results above show that in general EclipseLink with HSQLDB embedded is much more efficient than DataNucleus with H2 embedded in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with H2 embedded database (3.6) to the normalized speed of EclipseLink with HSQLDB embedded database (25.9) reveals that in these tests, EclipseLink with HSQLDB embedded is 7.2 times faster than DataNucleus with H2 embedded.

A huge performance gap has been detected when using class inheritance in the object model with large transaction size. Comparing the normalized speed of DataNucleus with H2 embedded database (1.3) to the normalized speed of EclipseLink with HSQLDB embedded database (23.9) reveals that in that case, EclipseLink with HSQLDB embedded is 18.4 times faster than DataNucleus with H2 embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded
Basic Person Test	41.4	27.0	41.4	27.0	41.4	27.0
Element Collection Test	46.9	22.4	46.9	22.4	46.9	22.4
Inheritance Test	41.4	27.0	41.4	27.0	41.4	27.0
Indexing Test	48.4	31.6	49.2	32.1	48.8	31.9
Graph (Binary Tree) Test	28.5	20.0	21.4	15.0	25.0	17.5
Multithreading Test	51.9	33.9	10.3	9.2	31.1	21.5
All Tests	43.1	27.0	35.1	22.1	39.1	24.6

The results above show that in general EclipseLink with HSQLDB embedded is more efficient than DataNucleus with H2 embedded in using disk space.

A large gap has been detected when using JPA element collections with small transaction size. Comparing the normalized score of DataNucleus with H2 embedded database (22.4) to the normalized score of EclipseLink with HSQLDB embedded database (46.9) reveals that in that case, EclipseLink with HSQLDB embedded is 2.1 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 HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded	EclipseLink HSQLDB embedded	DataNucleus H2 embedded
Basic Person Test	20.9	10.3	16.3	5.6	18.6	7.9
Element Collection Test	12.8	6.1	8.6	3.9	10.7	5.0
Inheritance Test	19.5	9.0	17.3	4.9	18.4	6.9
Indexing Test	28.0	10.1	24.9	7.6	26.5	8.9
Graph (Binary Tree) Test	10.0	7.8	11.9	8.7	11.0	8.3
Multithreading Test	27.0	16.5	14.6	5.9	20.8	11.2
All Tests	20.1	9.6	15.7	6.0	17.9	7.8

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

A large performance gap has been detected when using class inheritance in the object model with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (4.9) to the normalized speed of EclipseLink with HSQLDB embedded database (17.3) reveals that in that case, EclipseLink with HSQLDB embedded is 3.5 times faster than DataNucleus with H2 embedded.

JPA Performance Benchmark (JPAB)