Comparison of EclipseLink with MySQL server vs DataNucleus with H2 server

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 MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server
Basic Person Test	3.6	3.4	1.5	2.2	2.6	2.8
Element Collection Test	1.5	1.2	0.69	0.64	1.1	0.92
Inheritance Test	3.5	3.0	1.4	1.9	2.4	2.4
Indexing Test	5.3	5.3	2.5	3.5	3.9	4.4
Graph (Binary Tree) Test	1.7	2.1	1.3	1.3	1.5	1.7
Multithreading Test	7.2	10.0	2.4	4.3	4.8	7.2
All Tests	3.8	4.2	1.6	2.3	2.7	3.2

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server
Basic Person Test	0.43	2.5	15.5	5.2	8.0	3.9
Element Collection Test	0.16	0.56	1.4	1.1	0.78	0.82
Inheritance Test	0.39	2.2	17.6	6.1	9.0	4.2
Indexing Test	0.43	2.1	16.6	7.7	8.5	4.9
Graph (Binary Tree) Test	0.53	5.7	0.76	8.9	0.65	7.3
Multithreading Test	0.19	2.3	11.0	8.7	5.6	5.5
All Tests	0.35	2.5	10.5	6.3	5.4	4.4

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

A large performance gap has been detected when using simple basic entities with large retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (5.2) to the normalized speed of EclipseLink with MySQL database server (15.5) reveals that in that case, EclipseLink with MySQL server is 3.0 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with MySQL server is slower, for instance, when using multithreading with small retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.19) to the normalized speed of DataNucleus with H2 database server (2.3) reveals that in that case, EclipseLink with MySQL server is 12.1 times slower than DataNucleus with H2 server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server
Basic Person Test	1.5	4.1	0.44	1.3	0.95	2.7
Element Collection Test	1.4	4.0	0.43	0.49	0.92	2.3
Inheritance Test	1.1	2.9	0.61	1.5	0.86	2.2
Indexing Test	0.26	0.0036	0.52	1.5	0.39	0.75
Multithreading Test	1.9	1.3	0.72	failed	1.3	1.3
All Tests	1.2	2.5	0.54	1.2	0.88	1.9

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

The results above show that in general DataNucleus with H2 server is more efficient than EclipseLink with MySQL server in executing the tested JPA queries. Comparing the normalized speed of EclipseLink with MySQL database server (0.88) to the normalized speed of DataNucleus with H2 database server (1.9) reveals that in these tests, DataNucleus with H2 server is 2.2 times faster than EclipseLink with MySQL server.

A large performance gap has been detected when using simple basic entities with large retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.44) to the normalized speed of DataNucleus with H2 database server (1.3) reveals that in that case, DataNucleus with H2 server is 3.0 times faster than EclipseLink with MySQL server.

On the other hand, DataNucleus with H2 server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (0.0036) to the normalized speed of EclipseLink with MySQL database server (0.26) reveals that in that case, DataNucleus with H2 server is 72.2 times slower than EclipseLink with MySQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server
Basic Person Test	0.39	2.5	1.8	1.4	1.1	1.9
Element Collection Test	0.23	2.0	1.4	1.0	0.83	1.5
Inheritance Test	0.42	2.4	2.6	2.3	1.5	2.3
Indexing Test	0.46	2.7	3.1	3.0	1.8	2.9
Graph (Binary Tree) Test	0.67	1.8	0.41	0.60	0.54	1.2
Multithreading Test	0.48	failed	2.6	failed	1.5	failed
All Tests	0.44	2.3	2.0	1.7	1.2	2.0

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

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server
Basic Person Test	0.35	3.4	1.7	1.3	1.0	2.3
Element Collection Test	0.11	1.5	0.51	0.68	0.31	1.1
Inheritance Test	0.29	2.7	1.6	1.3	0.94	2.0
Indexing Test	0.46	5.7	1.9	1.9	1.2	3.8
Graph (Binary Tree) Test	0.54	1.5	0.49	1.2	0.51	1.3
Multithreading Test	0.31	failed	3.6	5.1	1.9	5.1
All Tests	0.34	3.0	1.6	1.9	0.98	2.4

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

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

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

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server	EclipseLink MySQL server	DataNucleus H2 server
Basic Person Test	1.3	3.2	4.2	2.3	2.7	2.7
Element Collection Test	0.69	1.9	0.89	0.78	0.79	1.3
Inheritance Test	1.1	2.6	4.8	2.6	2.9	2.6
Indexing Test	1.4	3.2	4.9	3.5	3.2	3.3
Graph (Binary Tree) Test	0.85	2.8	0.73	3.0	0.79	2.9
Multithreading Test	2.0	4.5	4.0	6.0	3.0	5.3
All Tests	1.2	2.9	3.3	2.8	2.3	2.9

The results above show that in general DataNucleus with H2 server is slightly more efficient than EclipseLink with MySQL server in performing JPA database operations.

A large performance gap has been detected when using graphs of objects with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.73) to the normalized speed of DataNucleus with H2 database server (3.0) reveals that in that case, DataNucleus with H2 server is 4.1 times faster than EclipseLink with MySQL server.

JPA Performance Benchmark (JPAB)