• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with MySQL server vs DataNucleus with Derby 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 MySQL server	DataNucleus Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded
Basic Person Test	3.6	4.6	1.5	2.8	2.6	3.7
Element Collection Test	1.5	2.4	0.69	1.6	1.1	2.0
Inheritance Test	3.5	4.6	1.4	2.7	2.4	3.7
Indexing Test	5.3	7.6	2.5	4.8	3.9	6.2
Graph (Binary Tree) Test	1.7	1.6	1.3	1.4	1.5	1.5
Multithreading Test	7.2	8.6	2.4	3.3	4.8	5.9
All Tests	3.8	4.9	1.6	2.8	2.7	3.8

The results above show that in general DataNucleus with Derby embedded 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 JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (0.69) to the normalized speed of DataNucleus with Derby embedded database (1.6) reveals that in that case, DataNucleus with Derby embedded is 2.3 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 Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded
Basic Person Test	0.43	6.8	15.5	14.9	8.0	10.9
Element Collection Test	0.16	5.4	1.4	7.6	0.78	6.5
Inheritance Test	0.39	8.8	17.6	14.8	9.0	11.8
Indexing Test	0.43	9.2	16.6	14.1	8.5	11.6
Graph (Binary Tree) Test	0.53	9.9	0.76	15.8	0.65	12.9
Multithreading Test	0.19	11.9	11.0	11.5	5.6	11.7
All Tests	0.35	8.7	10.5	13.1	5.4	10.9

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

A huge performance gap has been detected 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 Derby embedded database (11.9) reveals that in that case, DataNucleus with Derby embedded is 62.6 times faster than EclipseLink with MySQL 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 Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded
Basic Person Test	1.5	39.1	0.44	7.5	0.95	23.3
Element Collection Test	1.4	46.0	0.43	6.7	0.92	26.3
Inheritance Test	1.1	7.7	0.61	3.8	0.86	5.7
Indexing Test	0.26	0.053	0.52	8.0	0.39	4.0
Multithreading Test	1.9	failed	0.72	failed	1.3	failed
All Tests	1.2	23.2	0.54	6.5	0.88	14.8

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

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

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

On the other hand, DataNucleus with Derby embedded is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (0.053) to the normalized speed of EclipseLink with MySQL database server (0.26) reveals that in that case, DataNucleus with Derby embedded is 4.9 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 Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded
Basic Person Test	0.39	4.0	1.8	3.8	1.1	3.9
Element Collection Test	0.23	3.7	1.4	4.5	0.83	4.1
Inheritance Test	0.42	4.4	2.6	4.8	1.5	4.6
Indexing Test	0.46	5.2	3.1	4.2	1.8	4.7
Graph (Binary Tree) Test	0.67	2.7	0.41	1.5	0.54	2.1
Multithreading Test	0.48	failed	2.6	failed	1.5	failed
All Tests	0.44	4.0	2.0	3.7	1.2	3.9

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

The results above show that in general DataNucleus with Derby embedded is much more efficient than EclipseLink with MySQL server in updating JPA entity objects in the database. Comparing the normalized speed of EclipseLink with MySQL database server (1.2) to the normalized speed of DataNucleus with Derby embedded database (3.9) reveals that in these tests, DataNucleus with Derby embedded is 3.2 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.23) to the normalized speed of DataNucleus with Derby embedded database (3.7) reveals that in that case, DataNucleus with Derby embedded is 16.1 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 Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded
Basic Person Test	0.35	3.5	1.7	1.3	1.0	2.4
Element Collection Test	0.11	1.9	0.51	1.6	0.31	1.7
Inheritance Test	0.29	2.4	1.6	1.3	0.94	1.9
Indexing Test	0.46	6.6	1.9	1.9	1.2	4.3
Graph (Binary Tree) Test	0.54	0.81	0.49	0.93	0.51	0.87
Multithreading Test	0.31	failed	3.6	failed	1.9	failed
All Tests	0.34	3.0	1.6	1.4	0.98	2.2

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

The results above show that in general DataNucleus with Derby embedded 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 Derby embedded database (2.2) reveals that in these tests, DataNucleus with Derby embedded is 2.2 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 Derby embedded database (1.9) reveals that in that case, DataNucleus with Derby embedded is 17.3 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 Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded	EclipseLink MySQL server	DataNucleus Derby embedded
Basic Person Test	1.3	11.6	4.2	6.1	2.7	8.8
Element Collection Test	0.69	11.9	0.89	4.4	0.79	8.1
Inheritance Test	1.1	5.6	4.8	5.5	2.9	5.5
Indexing Test	1.4	5.7	4.9	6.6	3.2	6.2
Graph (Binary Tree) Test	0.85	3.7	0.73	4.9	0.79	4.3
Multithreading Test	2.0	10.3	4.0	7.4	3.0	8.8
All Tests	1.2	8.0	3.3	5.7	2.3	6.9

The results above show that in general DataNucleus with Derby embedded is much 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 Derby embedded database (6.9) reveals that in these tests, DataNucleus with Derby embedded is 3.0 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 Derby embedded database (11.9) reveals that in that case, DataNucleus with Derby embedded is 17.2 times faster 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.