Comparison of EclipseLink with MySQL server vs DataNucleus with PostgreSQL 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 PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server
Basic Person Test	3.6	4.1	1.5	2.6	2.6	3.3
Element Collection Test	1.5	0.91	0.69	0.38	1.1	0.64
Inheritance Test	3.5	3.8	1.4	2.4	2.4	3.1
Indexing Test	5.3	6.0	2.5	6.4	3.9	6.2
Graph (Binary Tree) Test	1.7	0.91	1.3	0.77	1.5	0.84
Multithreading Test	7.2	18.0	2.4	8.3	4.8	13.1
All Tests	3.8	5.6	1.6	3.5	2.7	4.5

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

A large performance gap has been detected when using multithreading with large transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (2.4) to the normalized speed of DataNucleus with PostgreSQL database server (8.3) reveals that in that case, DataNucleus with PostgreSQL server is 3.5 times faster than EclipseLink with MySQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server
Basic Person Test	0.43	1.7	15.5	7.6	8.0	4.6
Element Collection Test	0.16	0.73	1.4	0.63	0.78	0.68
Inheritance Test	0.39	1.5	17.6	9.3	9.0	5.4
Indexing Test	0.43	1.5	16.6	9.2	8.5	5.3
Graph (Binary Tree) Test	0.53	2.6	0.76	12.3	0.65	7.4
Multithreading Test	0.19	3.4	11.0	10.8	5.6	7.1
All Tests	0.35	1.9	10.5	8.3	5.4	5.1

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

A large performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.63) to the normalized speed of EclipseLink with MySQL database server (1.4) reveals that in that case, EclipseLink with MySQL server is 2.2 times faster than DataNucleus with PostgreSQL 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 PostgreSQL database server (3.4) reveals that in that case, EclipseLink with MySQL server is 17.9 times slower than DataNucleus with PostgreSQL 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 PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server
Basic Person Test	1.5	49.1	0.44	4.7	0.95	26.9
Element Collection Test	1.4	39.1	0.43	0.48	0.92	19.8
Inheritance Test	1.1	55.9	0.61	6.6	0.86	31.2
Indexing Test	0.26	0.048	0.52	6.4	0.39	3.2
Multithreading Test	1.9	failed	0.72	failed	1.3	failed
All Tests	1.2	36.0	0.54	4.5	0.88	20.3

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

The results above show that in general DataNucleus with PostgreSQL server is much 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 PostgreSQL database server (20.3) reveals that in these tests, DataNucleus with PostgreSQL server is 23.1 times faster than EclipseLink with MySQL server.

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (1.1) to the normalized speed of DataNucleus with PostgreSQL database server (55.9) reveals that in that case, DataNucleus with PostgreSQL server is 50.8 times faster than EclipseLink with MySQL server.

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.048) to the normalized speed of EclipseLink with MySQL database server (0.26) reveals that in that case, DataNucleus with PostgreSQL server is 5.4 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 PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server
Basic Person Test	0.39	2.1	1.8	0.84	1.1	1.5
Element Collection Test	0.23	1.4	1.4	0.64	0.83	1.0
Inheritance Test	0.42	2.1	2.6	1.2	1.5	1.7
Indexing Test	0.46	2.2	3.1	1.5	1.8	1.8
Graph (Binary Tree) Test	0.67	0.65	0.41	0.20	0.54	0.42
Multithreading Test	0.48	0.46	2.6	failed	1.5	0.46
All Tests	0.44	1.5	2.0	0.87	1.2	1.2

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

The results above show that in general DataNucleus with PostgreSQL server is equivalent to 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 PostgreSQL database server (1.4) reveals that in that case, DataNucleus with PostgreSQL server is 6.1 times faster than EclipseLink with MySQL server.

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.64) to the normalized speed of EclipseLink with MySQL database server (1.4) reveals that in that case, DataNucleus with PostgreSQL server is 2.2 times slower 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 PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server
Basic Person Test	0.35	3.0	1.7	1.3	1.0	2.2
Element Collection Test	0.11	1.0	0.51	0.39	0.31	0.69
Inheritance Test	0.29	2.8	1.6	1.3	0.94	2.1
Indexing Test	0.46	5.4	1.9	1.9	1.2	3.7
Graph (Binary Tree) Test	0.54	0.38	0.49	0.37	0.51	0.37
Multithreading Test	0.31	13.8	3.6	failed	1.9	13.8
All Tests	0.34	4.4	1.6	1.1	0.98	2.9

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

The results above show that in general DataNucleus with PostgreSQL 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 PostgreSQL database server (2.9) reveals that in these tests, DataNucleus with PostgreSQL server is 3.0 times faster than EclipseLink with MySQL server.

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (0.31) to the normalized speed of DataNucleus with PostgreSQL database server (13.8) reveals that in that case, DataNucleus with PostgreSQL server is 44.5 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 PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server	EclipseLink MySQL server	DataNucleus PostgreSQL server
Basic Person Test	1.3	12.0	4.2	3.4	2.7	7.7
Element Collection Test	0.69	8.6	0.89	0.50	0.79	4.6
Inheritance Test	1.1	13.2	4.8	4.2	2.9	8.7
Indexing Test	1.4	3.0	4.9	5.1	3.2	4.0
Graph (Binary Tree) Test	0.85	1.1	0.73	3.4	0.79	2.3
Multithreading Test	2.0	8.9	4.0	9.5	3.0	9.1
All Tests	1.2	8.0	3.3	3.8	2.3	6.0

The results above show that in general DataNucleus with PostgreSQL server is more efficient than EclipseLink with MySQL server in performing JPA database operations. Comparing the normalized speed of EclipseLink with MySQL database server (2.3) to the normalized speed of DataNucleus with PostgreSQL database server (6.0) reveals that in these tests, DataNucleus with PostgreSQL server is 2.6 times faster than EclipseLink with MySQL server.

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.69) to the normalized speed of DataNucleus with PostgreSQL database server (8.6) reveals that in that case, DataNucleus with PostgreSQL server is 12.5 times faster than EclipseLink with MySQL server.

JPA Performance Benchmark (JPAB)