• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of OpenJPA with Derby embedded vs DataNucleus with Derby 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
	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server
Basic Person Test	4.8	2.8	2.9	2.3	3.9	2.6
Element Collection Test	2.8	0.71	1.9	0.35	2.4	0.53
Inheritance Test	4.1	2.7	2.4	2.0	3.3	2.3
Indexing Test	6.1	4.5	4.1	4.0	5.1	4.3
Graph (Binary Tree) Test	1.5	0.62	1.4	0.53	1.4	0.57
Multithreading Test	8.7	4.9	3.3	3.4	6.0	4.1
All Tests	4.7	2.7	2.7	2.1	3.7	2.4

The results above show that in general OpenJPA with Derby embedded is more efficient than DataNucleus with Derby 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 Derby database server (0.35) to the normalized speed of OpenJPA with Derby embedded database (1.9) reveals that in that case, OpenJPA with Derby embedded is 5.4 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
	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server
Basic Person Test	14.8	0.56	22.6	6.3	18.7	3.4
Element Collection Test	0.0031	0.36	2.3	0.93	1.2	0.64
Inheritance Test	0.015	0.45	7.0	6.8	3.5	3.6
Indexing Test	11.7	0.50	26.5	7.1	19.1	3.8
Graph (Binary Tree) Test	0.93	0.22	1.2	6.6	1.1	3.4
Multithreading Test	25.2	1.2	28.6	10.0	26.9	5.6
All Tests	8.8	0.55	14.7	6.3	11.7	3.4

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

A huge performance gap has been detected when using simple basic entities with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.56) to the normalized speed of OpenJPA with Derby embedded database (14.8) reveals that in that case, OpenJPA with Derby embedded is 26.4 times faster than DataNucleus with Derby server.

On the other hand, OpenJPA with Derby embedded is slower, for instance, when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with Derby embedded database (0.0031) to the normalized speed of DataNucleus with Derby database server (0.36) reveals that in that case, OpenJPA with Derby embedded is 116 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
	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server
Basic Person Test	49.7	37.7	9.9	3.6	29.8	20.7
Element Collection Test	2.7	25.9	9.6	1.4	6.1	13.6
Inheritance Test	2.3	6.5	1.3	1.8	1.8	4.2
Indexing Test	7.0	0.030	17.1	4.9	12.1	2.5
Multithreading Test	40.9	failed	11.7	failed	26.3	failed
All Tests	20.5	17.5	9.9	2.9	15.2	10.2

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

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

On the other hand, OpenJPA with Derby embedded is slower, for instance, when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with Derby embedded database (2.7) to the normalized speed of DataNucleus with Derby database server (25.9) reveals that in that case, OpenJPA with Derby embedded is 9.6 times slower than DataNucleus with Derby server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server
Basic Person Test	5.6	1.1	5.2	0.85	5.4	0.99
Element Collection Test	0.0090	0.81	2.2	0.62	1.1	0.71
Inheritance Test	0.045	1.2	4.6	1.3	2.3	1.2
Indexing Test	6.1	1.2	8.7	1.5	7.4	1.3
Graph (Binary Tree) Test	1.6	0.29	0.91	0.41	1.3	0.35
Multithreading Test	18.3	failed	4.5	failed	11.4	failed
All Tests	5.3	0.93	4.4	0.92	4.8	0.92

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

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

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

On the other hand, OpenJPA with Derby embedded is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with Derby embedded database (0.0090) to the normalized speed of DataNucleus with Derby database server (0.81) reveals that in that case, OpenJPA with Derby embedded is 90.0 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
	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server
Basic Person Test	4.2	1.3	4.5	1.3	4.3	1.3
Element Collection Test	0.0071	0.61	1.6	0.33	0.80	0.47
Inheritance Test	0.035	1.0	3.0	1.3	1.5	1.2
Indexing Test	5.3	2.3	3.6	1.9	4.4	2.1
Graph (Binary Tree) Test	0.80	0.26	0.93	0.46	0.86	0.36
Multithreading Test	5.7	failed	6.2	failed	6.0	failed
All Tests	2.7	1.1	3.3	1.1	3.0	1.1

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

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

A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.33) to the normalized speed of OpenJPA with Derby embedded database (1.6) reveals that in that case, OpenJPA with Derby embedded is 4.8 times faster than DataNucleus with Derby server.

On the other hand, OpenJPA with Derby embedded is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with Derby embedded database (0.0071) to the normalized speed of DataNucleus with Derby database server (0.61) reveals that in that case, OpenJPA with Derby embedded is 85.9 times slower than DataNucleus with Derby server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server	OpenJPA Derby embedded	DataNucleus Derby server
Basic Person Test	15.8	8.7	9.0	2.9	12.4	5.8
Element Collection Test	1.1	5.7	3.5	0.72	2.3	3.2
Inheritance Test	1.3	2.4	3.7	2.6	2.5	2.5
Indexing Test	7.2	1.7	12.0	3.9	9.6	2.8
Graph (Binary Tree) Test	1.2	0.35	1.1	2.0	1.2	1.2
Multithreading Test	19.8	3.0	10.9	6.7	15.3	4.9
All Tests	8.0	3.8	6.9	2.8	7.4	3.3

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

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (3.0) to the normalized speed of OpenJPA with Derby embedded database (19.8) reveals that in that case, OpenJPA with Derby embedded is 6.6 times faster than DataNucleus with Derby server.

On the other hand, OpenJPA with Derby embedded is slower, for instance, when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with Derby embedded database (1.1) to the normalized speed of DataNucleus with Derby database server (5.7) reveals that in that case, OpenJPA with Derby embedded is 5.2 times slower than DataNucleus 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.