Comparison of DataNucleus with Derby embedded vs DataNucleus 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 embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server
Basic Person Test	4.6	2.6	2.8	1.4	3.7	2.0
Element Collection Test	2.4	1.0	1.6	0.48	2.0	0.76
Inheritance Test	4.6	2.5	2.7	1.3	3.7	1.9
Indexing Test	7.6	4.0	4.8	2.5	6.2	3.3
Graph (Binary Tree) Test	1.6	1.1	1.4	0.99	1.5	1.1
Multithreading Test	8.6	6.2	3.3	2.5	5.9	4.4
All Tests	4.9	2.9	2.8	1.5	3.8	2.2

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server
Basic Person Test	6.8	0.96	14.9	9.3	10.9	5.1
Element Collection Test	5.4	0.18	7.6	0.77	6.5	0.47
Inheritance Test	8.8	0.55	14.8	8.5	11.8	4.5
Indexing Test	9.2	0.82	14.1	9.7	11.6	5.3
Graph (Binary Tree) Test	9.9	2.1	15.8	3.5	12.9	2.8
Multithreading Test	11.9	0.27	11.5	7.8	11.7	4.0
All Tests	8.7	0.81	13.1	6.6	10.9	3.7

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

A huge performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.27) to the normalized speed of DataNucleus with Derby embedded database (11.9) reveals that in that case, DataNucleus with Derby embedded is 44.1 times faster than DataNucleus with MySQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server
Basic Person Test	39.1	7.2	7.5	2.2	23.3	4.7
Element Collection Test	46.0	5.8	6.7	0.27	26.3	3.1
Inheritance Test	7.7	2.9	3.8	1.7	5.7	2.3
Indexing Test	0.053	0.0084	8.0	2.5	4.0	1.2
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	23.2	4.0	6.5	1.7	14.8	2.8

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

The results above show that in general DataNucleus with Derby embedded is much more efficient than DataNucleus with MySQL server in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with MySQL database server (2.8) to the normalized speed of DataNucleus with Derby embedded database (14.8) reveals that in these tests, DataNucleus with Derby embedded is 5.3 times faster than DataNucleus with MySQL server.

A huge performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.27) to the normalized speed of DataNucleus with Derby embedded database (6.7) reveals that in that case, DataNucleus with Derby embedded is 24.8 times faster than DataNucleus 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 embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server
Basic Person Test	4.0	0.61	3.8	1.1	3.9	0.88
Element Collection Test	3.7	0.31	4.5	0.44	4.1	0.38
Inheritance Test	4.4	0.51	4.8	1.8	4.6	1.1
Indexing Test	5.2	0.68	4.2	2.2	4.7	1.5
Graph (Binary Tree) Test	2.7	0.91	1.5	0.47	2.1	0.69
Multithreading Test	failed	0.64	failed	failed	failed	0.64
All Tests	4.0	0.61	3.7	1.2	3.9	0.88

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

The results above show that in general DataNucleus with Derby embedded is much more efficient than DataNucleus with MySQL server in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with MySQL database server (0.88) to the normalized speed of DataNucleus with Derby embedded database (3.9) reveals that in these tests, DataNucleus with Derby embedded is 4.4 times faster than DataNucleus with MySQL server.

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server
Basic Person Test	3.5	0.70	1.3	1.3	2.4	1.0
Element Collection Test	1.9	0.17	1.6	0.40	1.7	0.29
Inheritance Test	2.4	0.41	1.3	1.3	1.9	0.87
Indexing Test	6.6	1.7	1.9	1.9	4.3	1.8
Graph (Binary Tree) Test	0.81	0.49	0.93	0.46	0.87	0.47
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	3.0	0.69	1.4	1.1	2.2	0.89

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

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of DataNucleus with MySQL database server (0.17) to the normalized speed of DataNucleus with Derby embedded database (1.9) reveals that in that case, DataNucleus with Derby embedded is 11.2 times faster than DataNucleus 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 embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server	DataNucleus Derby embedded	DataNucleus MySQL server
Basic Person Test	11.6	2.4	6.1	3.1	8.8	2.7
Element Collection Test	11.9	1.5	4.4	0.47	8.1	0.99
Inheritance Test	5.6	1.4	5.5	2.9	5.5	2.1
Indexing Test	5.7	1.4	6.6	3.8	6.2	2.6
Graph (Binary Tree) Test	3.7	1.2	4.9	1.4	4.3	1.3
Multithreading Test	10.3	2.4	7.4	5.1	8.8	3.5
All Tests	8.0	1.7	5.7	2.6	6.9	2.1

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

A large performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with MySQL database server (0.47) to the normalized speed of DataNucleus with Derby embedded database (4.4) reveals that in that case, DataNucleus with Derby embedded is 9.4 times faster than DataNucleus with MySQL server.

JPA Performance Benchmark (JPAB)