• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with MySQL server vs DataNucleus with DB4O 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 DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded
Basic Person Test	3.6	0.059	1.5	1.3	2.6	0.69
Element Collection Test	1.5	0.045	0.69	1.0	1.1	0.52
Inheritance Test	3.5	0.051	1.4	0.85	2.4	0.45
Indexing Test	5.3	0.080	2.5	2.3	3.9	1.2
Graph (Binary Tree) Test	1.7	failed	1.3	failed	1.5	failed
Multithreading Test	7.2	failed	2.4	failed	4.8	failed
All Tests	3.8	0.059	1.6	1.4	2.7	0.71

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.051) to the normalized speed of EclipseLink with MySQL database server (3.5) reveals that in that case, EclipseLink with MySQL server is 68.6 times faster than DataNucleus with DB4O embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded
Basic Person Test	0.43	0.0047	15.5	1.8	8.0	0.90
Element Collection Test	0.16	0.0038	1.4	1.5	0.78	0.77
Inheritance Test	0.39	0.0035	17.6	2.2	9.0	1.1
Indexing Test	0.43	0.0043	16.6	1.8	8.5	0.89
Graph (Binary Tree) Test	0.53	failed	0.76	failed	0.65	failed
Multithreading Test	0.19	failed	11.0	failed	5.6	failed
All Tests	0.35	0.0041	10.5	1.8	5.4	0.91

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded
Basic Person Test	1.5	failed	0.44	failed	0.95	failed
Element Collection Test	1.4	failed	0.43	failed	0.92	failed
Inheritance Test	1.1	failed	0.61	failed	0.86	failed
Indexing Test	0.26	failed	0.52	failed	0.39	failed
Multithreading Test	1.9	failed	0.72	failed	1.3	failed
All Tests	1.2	failed	0.54	failed	0.88	failed

DataNucleus with DB4O embedded has failed in 10 tests (see exceptions).

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded
Basic Person Test	0.39	0.012	1.8	0.76	1.1	0.39
Element Collection Test	0.23	0.012	1.4	1.1	0.83	0.53
Inheritance Test	0.42	0.011	2.6	0.81	1.5	0.41
Indexing Test	0.46	0.011	3.1	1.3	1.8	0.64
Graph (Binary Tree) Test	0.67	failed	0.41	failed	0.54	failed
Multithreading Test	0.48	failed	2.6	failed	1.5	failed
All Tests	0.44	0.012	2.0	0.97	1.2	0.49

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.011) to the normalized speed of EclipseLink with MySQL database server (0.46) reveals that in that case, EclipseLink with MySQL server is 41.8 times faster than DataNucleus with DB4O embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded
Basic Person Test	0.35	0.011	1.7	1.5	1.0	0.74
Element Collection Test	0.11	0.010	0.51	1.6	0.31	0.80
Inheritance Test	0.29	0.0093	1.6	1.1	0.94	0.57
Indexing Test	0.46	0.017	1.9	2.1	1.2	1.1
Graph (Binary Tree) Test	0.54	failed	0.49	failed	0.51	failed
Multithreading Test	0.31	failed	3.6	failed	1.9	failed
All Tests	0.34	0.012	1.6	1.6	0.98	0.79

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.011) to the normalized speed of EclipseLink with MySQL database server (0.35) reveals that in that case, EclipseLink with MySQL server is 31.8 times faster than DataNucleus with DB4O embedded.

On the other hand, EclipseLink with MySQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (0.51) to the normalized speed of DataNucleus with DB4O embedded database (1.6) reveals that in that case, EclipseLink with MySQL server is 3.1 times slower than DataNucleus with DB4O embedded.

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 DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded	EclipseLink MySQL server	DataNucleus DB4O embedded
Basic Person Test	1.3	0.022	4.2	1.3	2.7	0.68
Element Collection Test	0.69	0.018	0.89	1.3	0.79	0.66
Inheritance Test	1.1	0.019	4.8	1.2	2.9	0.63
Indexing Test	1.4	0.028	4.9	1.9	3.2	0.94
Graph (Binary Tree) Test	0.85	failed	0.73	failed	0.79	failed
Multithreading Test	2.0	failed	4.0	failed	3.0	failed
All Tests	1.2	0.022	3.3	1.4	2.3	0.73

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

A huge performance gap has been detected when using simple basic entities with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.022) to the normalized speed of EclipseLink with MySQL database server (1.3) reveals that in that case, EclipseLink with MySQL server is 59.1 times faster than DataNucleus with DB4O embedded.

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.