• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with Derby 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 Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded
Basic Person Test	3.8	4.6	3.1	2.8	3.4	3.7
Element Collection Test	2.2	2.4	1.5	1.6	1.8	2.0
Inheritance Test	3.9	4.6	2.9	2.7	3.4	3.7
Indexing Test	5.2	7.6	4.3	4.8	4.7	6.2
Graph (Binary Tree) Test	1.9	1.6	1.7	1.4	1.8	1.5
Multithreading Test	6.1	8.6	3.9	3.3	5.0	5.9
All Tests	3.8	4.9	2.9	2.8	3.4	3.8

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded
Basic Person Test	6.4	6.8	11.3	14.9	8.8	10.9
Element Collection Test	1.8	5.4	2.4	7.6	2.1	6.5
Inheritance Test	3.7	8.8	12.9	14.8	8.3	11.8
Indexing Test	3.6	9.2	12.8	14.1	8.2	11.6
Graph (Binary Tree) Test	0.61	9.9	0.73	15.8	0.67	12.9
Multithreading Test	8.5	11.9	19.8	11.5	14.1	11.7
All Tests	4.1	8.7	10.0	13.1	7.0	10.9

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

A huge performance gap has been detected when using graphs of objects with large retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (0.73) to the normalized speed of DataNucleus with Derby embedded database (15.8) reveals that in that case, DataNucleus with Derby embedded is 21.6 times faster than EclipseLink with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded
Basic Person Test	45.8	39.1	5.3	7.5	25.6	23.3
Element Collection Test	35.2	46.0	0.99	6.7	18.1	26.3
Inheritance Test	23.1	7.7	5.9	3.8	14.5	5.7
Indexing Test	2.5	0.053	12.2	8.0	7.4	4.0
Multithreading Test	34.3	failed	7.7	failed	21.0	failed
All Tests	28.2	23.2	6.4	6.5	17.3	14.8

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

The results above show that in general EclipseLink with Derby server is slightly more efficient than DataNucleus with Derby embedded in executing the tested JPA queries.

A huge performance gap has been detected 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 Derby database server (2.5) reveals that in that case, EclipseLink with Derby server is 47.2 times faster than DataNucleus with Derby embedded.

On the other hand, EclipseLink with Derby server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (0.99) to the normalized speed of DataNucleus with Derby embedded database (6.7) reveals that in that case, EclipseLink with Derby server is 6.8 times slower than DataNucleus with Derby embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded
Basic Person Test	3.9	4.0	4.4	3.8	4.1	3.9
Element Collection Test	1.7	3.7	1.6	4.5	1.6	4.1
Inheritance Test	4.6	4.4	6.1	4.8	5.3	4.6
Indexing Test	4.5	5.2	7.6	4.2	6.1	4.7
Graph (Binary Tree) Test	0.70	2.7	0.42	1.5	0.56	2.1
Multithreading Test	7.3	failed	4.8	failed	6.0	failed
All Tests	3.8	4.0	4.2	3.7	4.0	3.9

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

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

On the other hand, EclipseLink with Derby server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of EclipseLink with Derby database server (0.70) to the normalized speed of DataNucleus with Derby embedded database (2.7) reveals that in that case, EclipseLink with Derby server is 3.9 times slower than DataNucleus with Derby embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded
Basic Person Test	2.8	3.5	3.9	1.3	3.3	2.4
Element Collection Test	1.2	1.9	0.55	1.6	0.87	1.7
Inheritance Test	3.3	2.4	3.7	1.3	3.5	1.9
Indexing Test	4.9	6.6	3.5	1.9	4.2	4.3
Graph (Binary Tree) Test	0.51	0.81	0.50	0.93	0.51	0.87
Multithreading Test	4.8	failed	5.7	failed	5.3	failed
All Tests	2.9	3.0	3.0	1.4	3.0	2.2

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

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

A large performance gap has been detected when using simple basic entities with large transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (1.3) to the normalized speed of EclipseLink with Derby database server (3.9) reveals that in that case, EclipseLink with Derby server is 3.0 times faster than DataNucleus with Derby embedded.

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

Comparison of JPA/Database speed - the averages (normalized score, higher is better)

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded	EclipseLink Derby server	DataNucleus Derby embedded
Basic Person Test	12.5	11.6	5.6	6.1	9.1	8.8
Element Collection Test	8.4	11.9	1.4	4.4	4.9	8.1
Inheritance Test	7.7	5.6	6.3	5.5	7.0	5.5
Indexing Test	4.1	5.7	8.1	6.6	6.1	6.2
Graph (Binary Tree) Test	0.93	3.7	0.83	4.9	0.88	4.3
Multithreading Test	12.2	10.3	8.4	7.4	10.3	8.8
All Tests	7.9	8.0	5.2	5.7	6.6	6.9

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

A large performance gap has been detected when using graphs of objects with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (0.83) to the normalized speed of DataNucleus with Derby embedded database (4.9) reveals that in that case, DataNucleus with Derby embedded is 5.9 times faster than EclipseLink with Derby 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.