• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus with Derby server vs EclipseLink with MySQL 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
	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server
Basic Person Test	2.8	3.6	2.3	1.5	2.6	2.6
Element Collection Test	0.71	1.5	0.35	0.69	0.53	1.1
Inheritance Test	2.7	3.5	2.0	1.4	2.3	2.4
Indexing Test	4.5	5.3	4.0	2.5	4.3	3.9
Graph (Binary Tree) Test	0.62	1.7	0.53	1.3	0.57	1.5
Multithreading Test	4.9	7.2	3.4	2.4	4.1	4.8
All Tests	2.7	3.8	2.1	1.6	2.4	2.7

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

A large performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.62) to the normalized speed of EclipseLink with MySQL database server (1.7) reveals that in that case, EclipseLink with MySQL server is 2.7 times faster than DataNucleus with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server
Basic Person Test	0.56	0.43	6.3	15.5	3.4	8.0
Element Collection Test	0.36	0.16	0.93	1.4	0.64	0.78
Inheritance Test	0.45	0.39	6.8	17.6	3.6	9.0
Indexing Test	0.50	0.43	7.1	16.6	3.8	8.5
Graph (Binary Tree) Test	0.22	0.53	6.6	0.76	3.4	0.65
Multithreading Test	1.2	0.19	10.0	11.0	5.6	5.6
All Tests	0.55	0.35	6.3	10.5	3.4	5.4

The results above show that in general EclipseLink with MySQL server is more efficient than DataNucleus with Derby server 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 Derby database server (6.8) to the normalized speed of EclipseLink with MySQL database server (17.6) reveals that in that case, EclipseLink with MySQL server is 2.6 times faster than DataNucleus with Derby server.

On the other hand, EclipseLink with MySQL server is slower, for instance, when using graphs of objects with large retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.76) to the normalized speed of DataNucleus with Derby database server (6.6) reveals that in that case, EclipseLink with MySQL server is 8.7 times slower than DataNucleus with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server
Basic Person Test	37.7	1.5	3.6	0.44	20.7	0.95
Element Collection Test	25.9	1.4	1.4	0.43	13.6	0.92
Inheritance Test	6.5	1.1	1.8	0.61	4.2	0.86
Indexing Test	0.030	0.26	4.9	0.52	2.5	0.39
Multithreading Test	failed	1.9	failed	0.72	failed	1.3
All Tests	17.5	1.2	2.9	0.54	10.2	0.88

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

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

A huge performance gap has been detected when using simple basic entities with small retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (1.5) to the normalized speed of DataNucleus with Derby database server (37.7) reveals that in that case, DataNucleus with Derby server is 25.1 times faster than EclipseLink with MySQL server.

On the other hand, DataNucleus with Derby server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.030) to the normalized speed of EclipseLink with MySQL database server (0.26) reveals that in that case, DataNucleus with Derby server is 8.7 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
	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server
Basic Person Test	1.1	0.39	0.85	1.8	0.99	1.1
Element Collection Test	0.81	0.23	0.62	1.4	0.71	0.83
Inheritance Test	1.2	0.42	1.3	2.6	1.2	1.5
Indexing Test	1.2	0.46	1.5	3.1	1.3	1.8
Graph (Binary Tree) Test	0.29	0.67	0.41	0.41	0.35	0.54
Multithreading Test	failed	0.48	failed	2.6	failed	1.5
All Tests	0.93	0.44	0.92	2.0	0.92	1.2

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

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

A large performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.29) to the normalized speed of EclipseLink with MySQL database server (0.67) reveals that in that case, EclipseLink with MySQL server is 2.3 times faster than DataNucleus with Derby server.

On the other hand, EclipseLink with MySQL server is slower, for instance, 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 Derby database server (0.81) reveals that in that case, EclipseLink with MySQL server is 3.5 times slower than DataNucleus with Derby server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server
Basic Person Test	1.3	0.35	1.3	1.7	1.3	1.0
Element Collection Test	0.61	0.11	0.33	0.51	0.47	0.31
Inheritance Test	1.0	0.29	1.3	1.6	1.2	0.94
Indexing Test	2.3	0.46	1.9	1.9	2.1	1.2
Graph (Binary Tree) Test	0.26	0.54	0.46	0.49	0.36	0.51
Multithreading Test	failed	0.31	failed	3.6	failed	1.9
All Tests	1.1	0.34	1.1	1.6	1.1	0.98

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

The results above show that in general DataNucleus with Derby server is slightly more efficient than EclipseLink with MySQL server in deleting JPA entity objects from 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.11) to the normalized speed of DataNucleus with Derby database server (0.61) reveals that in that case, DataNucleus with Derby server is 5.5 times faster than EclipseLink with MySQL server.

On the other hand, DataNucleus with Derby server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.26) to the normalized speed of EclipseLink with MySQL database server (0.54) reveals that in that case, DataNucleus with Derby server is 2.1 times slower 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
	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server	DataNucleus Derby server	EclipseLink MySQL server
Basic Person Test	8.7	1.3	2.9	4.2	5.8	2.7
Element Collection Test	5.7	0.69	0.72	0.89	3.2	0.79
Inheritance Test	2.4	1.1	2.6	4.8	2.5	2.9
Indexing Test	1.7	1.4	3.9	4.9	2.8	3.2
Graph (Binary Tree) Test	0.35	0.85	2.0	0.73	1.2	0.79
Multithreading Test	3.0	2.0	6.7	4.0	4.9	3.0
All Tests	3.8	1.2	2.8	3.3	3.3	2.3

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

A large 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 Derby database server (5.7) reveals that in that case, DataNucleus with Derby server is 8.3 times faster than EclipseLink with MySQL server.

On the other hand, DataNucleus with Derby server is slower, for instance, when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.35) to the normalized speed of EclipseLink with MySQL database server (0.85) reveals that in that case, DataNucleus with Derby server is 2.4 times slower than EclipseLink with MySQL server.

Other Head to Head DBMS/JPA Comparisons

JPA Performance Benchmark - Copyright © 2010, 2011, 2012 ObjectDB Software Ltd. - All rights reserved.
The benchmark program is released as open source under the GPL license.