Comparison of DataNucleus with MySQL server 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 MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded
Basic Person Test	2.6	25.1	1.4	8.9	2.0	17.0
Element Collection Test	1.0	20.4	0.48	8.0	0.76	14.2
Inheritance Test	2.5	28.7	1.3	8.7	1.9	18.7
Indexing Test	4.0	37.6	2.5	14.0	3.3	25.8
Graph (Binary Tree) Test	1.1	17.7	0.99	14.7	1.1	16.2
Multithreading Test	6.2	30.3	2.5	11.4	4.4	20.8
All Tests	2.9	26.6	1.5	10.9	2.2	18.8

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (1.0) to the normalized speed of EclipseLink with H2 embedded database (20.4) reveals that in that case, EclipseLink with H2 embedded is 20.4 times faster than DataNucleus with MySQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded
Basic Person Test	0.96	30.4	9.3	29.1	5.1	29.7
Element Collection Test	0.18	19.6	0.77	27.6	0.47	23.6
Inheritance Test	0.55	33.8	8.5	39.8	4.5	36.8
Indexing Test	0.82	22.2	9.7	41.3	5.3	31.8
Graph (Binary Tree) Test	2.1	16.0	3.5	20.0	2.8	18.0
Multithreading Test	0.27	33.7	7.8	29.0	4.0	31.4
All Tests	0.81	25.9	6.6	31.1	3.7	28.5

The results above show that in general EclipseLink with H2 embedded is much more efficient than DataNucleus with MySQL server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with MySQL database server (3.7) to the normalized speed of EclipseLink with H2 embedded database (28.5) reveals that in these tests, EclipseLink with H2 embedded is 7.7 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.27) to the normalized speed of EclipseLink with H2 embedded database (33.7) reveals that in that case, EclipseLink with H2 embedded is 125 times faster than DataNucleus with MySQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded
Basic Person Test	7.2	4.4	2.2	1.4	4.7	2.9
Element Collection Test	5.8	4.1	0.27	2.4	3.1	3.2
Inheritance Test	2.9	3.4	1.7	2.0	2.3	2.7
Indexing Test	0.0084	13.0	2.5	22.8	1.2	17.9
Multithreading Test	failed	1.0	failed	0.67	failed	0.85
All Tests	4.0	5.2	1.7	5.9	2.8	5.5

DataNucleus with MySQL server has failed in 2 tests (see exceptions).

The results above show that in general EclipseLink with H2 embedded is more efficient than DataNucleus with MySQL server in executing the tested JPA queries.

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.0084) to the normalized speed of EclipseLink with H2 embedded database (13.0) reveals that in that case, EclipseLink with H2 embedded is 1,548 times faster than DataNucleus with MySQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded
Basic Person Test	0.61	16.6	1.1	7.6	0.88	12.1
Element Collection Test	0.31	15.3	0.44	10.5	0.38	12.9
Inheritance Test	0.51	15.7	1.8	9.8	1.1	12.7
Indexing Test	0.68	12.1	2.2	9.9	1.5	11.0
Graph (Binary Tree) Test	0.91	13.7	0.47	7.0	0.69	10.3
Multithreading Test	0.64	20.9	failed	4.2	0.64	12.6
All Tests	0.61	15.7	1.2	8.2	0.88	12.0

DataNucleus with MySQL server has failed in 1 tests (see exceptions).

The results above show that in general EclipseLink with H2 embedded is much more efficient than DataNucleus with MySQL server in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with MySQL database server (0.88) to the normalized speed of EclipseLink with H2 embedded database (12.0) reveals that in these tests, EclipseLink with H2 embedded is 13.6 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (0.31) to the normalized speed of EclipseLink with H2 embedded database (15.3) reveals that in that case, EclipseLink with H2 embedded is 49.4 times faster than DataNucleus with MySQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded
Basic Person Test	0.70	35.1	1.3	19.6	1.0	27.4
Element Collection Test	0.17	19.3	0.40	8.5	0.29	13.9
Inheritance Test	0.41	36.0	1.3	14.0	0.87	25.0
Indexing Test	1.7	42.5	1.9	19.2	1.8	30.9
Graph (Binary Tree) Test	0.49	12.2	0.46	14.4	0.47	13.3
Multithreading Test	failed	54.4	failed	25.8	failed	40.1
All Tests	0.69	33.3	1.1	16.9	0.89	25.1

DataNucleus with MySQL server has failed in 2 tests (see exceptions).

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (0.17) to the normalized speed of EclipseLink with H2 embedded database (19.3) reveals that in that case, EclipseLink with H2 embedded is 114 times faster than DataNucleus with MySQL server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded	DataNucleus MySQL server	EclipseLink H2 embedded
Basic Person Test	2.4	22.3	3.1	13.3	2.7	17.8
Element Collection Test	1.5	15.7	0.47	11.4	0.99	13.6
Inheritance Test	1.4	23.5	2.9	14.9	2.1	19.2
Indexing Test	1.4	25.5	3.8	21.5	2.6	23.5
Graph (Binary Tree) Test	1.2	14.9	1.4	14.0	1.3	14.5
Multithreading Test	2.4	28.1	5.1	14.2	3.5	21.1
All Tests	1.7	21.9	2.6	14.9	2.1	18.4

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

A huge performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.47) to the normalized speed of EclipseLink with H2 embedded database (11.4) reveals that in that case, EclipseLink with H2 embedded is 24.3 times faster than DataNucleus with MySQL server.

JPA Performance Benchmark (JPAB)