Comparison of DataNucleus with Derby server vs OpenJPA with PostgreSQL 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 server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server
Basic Person Test	2.8	5.2	2.3	4.8	2.6	5.0
Element Collection Test	0.71	2.8	0.35	2.2	0.53	2.5
Inheritance Test	2.7	4.6	2.0	3.2	2.3	3.9
Indexing Test	4.5	7.4	4.0	6.9	4.3	7.1
Graph (Binary Tree) Test	0.62	0.98	0.53	0.81	0.57	0.89
Multithreading Test	4.9	23.4	3.4	9.1	4.1	16.2
All Tests	2.7	7.4	2.1	4.5	2.4	5.9

The results above show that in general OpenJPA with PostgreSQL server is more efficient than DataNucleus with Derby server in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with Derby database server (2.4) to the normalized speed of OpenJPA with PostgreSQL database server (5.9) reveals that in these tests, OpenJPA with PostgreSQL server is 2.5 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.35) to the normalized speed of OpenJPA with PostgreSQL database server (2.2) reveals that in that case, OpenJPA with PostgreSQL server is 6.3 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
	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server
Basic Person Test	0.56	5.8	6.3	16.1	3.4	10.9
Element Collection Test	0.36	0.013	0.93	8.7	0.64	4.4
Inheritance Test	0.45	5.2	6.8	17.6	3.6	11.4
Indexing Test	0.50	4.8	7.1	18.7	3.8	11.8
Graph (Binary Tree) Test	0.22	0.27	6.6	0.35	3.4	0.31
Multithreading Test	1.2	11.9	10.0	23.3	5.6	17.6
All Tests	0.55	4.7	6.3	14.1	3.4	9.4

The results above show that in general OpenJPA with PostgreSQL server is 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 PostgreSQL database server (9.4) reveals that in these tests, OpenJPA with PostgreSQL server is 2.8 times faster than DataNucleus with Derby server.

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 Derby database server (0.45) to the normalized speed of OpenJPA with PostgreSQL database server (5.2) reveals that in that case, OpenJPA with PostgreSQL server is 11.6 times faster than DataNucleus with Derby server.

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.013) to the normalized speed of DataNucleus with Derby database server (0.36) reveals that in that case, OpenJPA with PostgreSQL server is 27.7 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
	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server
Basic Person Test	37.7	failed	3.6	failed	20.7	failed
Element Collection Test	25.9	failed	1.4	failed	13.6	failed
Inheritance Test	6.5	failed	1.8	failed	4.2	failed
Indexing Test	0.030	failed	4.9	failed	2.5	failed
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	17.5	failed	2.9	failed	10.2	failed

DataNucleus with Derby server has failed in 2 tests (see exceptions). OpenJPA with PostgreSQL server 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
	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server
Basic Person Test	1.1	4.9	0.85	3.9	0.99	4.4
Element Collection Test	0.81	0.033	0.62	4.6	0.71	2.3
Inheritance Test	1.2	4.8	1.3	4.9	1.2	4.9
Indexing Test	1.2	5.1	1.5	6.0	1.3	5.6
Graph (Binary Tree) Test	0.29	0.57	0.41	0.31	0.35	0.44
Multithreading Test	failed	22.2	failed	7.4	failed	14.8
All Tests	0.93	6.3	0.92	4.5	0.92	5.4

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

The results above show that in general OpenJPA with PostgreSQL server 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 PostgreSQL database server (5.4) reveals that in these tests, OpenJPA with PostgreSQL server is 5.9 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.62) to the normalized speed of OpenJPA with PostgreSQL database server (4.6) reveals that in that case, OpenJPA with PostgreSQL server is 7.4 times faster than DataNucleus with Derby server.

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.033) to the normalized speed of DataNucleus with Derby database server (0.81) reveals that in that case, OpenJPA with PostgreSQL server is 24.5 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
	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server
Basic Person Test	1.3	4.6	1.3	5.3	1.3	5.0
Element Collection Test	0.61	0.032	0.33	2.8	0.47	1.4
Inheritance Test	1.0	4.3	1.3	4.6	1.2	4.4
Indexing Test	2.3	8.0	1.9	7.1	2.1	7.5
Graph (Binary Tree) Test	0.26	0.53	0.46	0.55	0.36	0.54
Multithreading Test	failed	17.4	failed	9.1	failed	13.3
All Tests	1.1	5.8	1.1	4.9	1.1	5.4

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

The results above show that in general OpenJPA with PostgreSQL server is much 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 PostgreSQL database server (5.4) reveals that in these tests, OpenJPA with PostgreSQL server is 4.9 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 PostgreSQL database server (2.8) reveals that in that case, OpenJPA with PostgreSQL server is 8.5 times faster than DataNucleus with Derby server.

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.032) to the normalized speed of DataNucleus with Derby database server (0.61) reveals that in that case, OpenJPA with PostgreSQL server is 19.1 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
	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server	DataNucleus Derby server	OpenJPA PostgreSQL server
Basic Person Test	8.7	5.1	2.9	7.5	5.8	6.3
Element Collection Test	5.7	0.72	0.72	4.6	3.2	2.6
Inheritance Test	2.4	4.7	2.6	7.6	2.5	6.2
Indexing Test	1.7	6.3	3.9	9.7	2.8	8.0
Graph (Binary Tree) Test	0.35	0.59	2.0	0.50	1.2	0.55
Multithreading Test	3.0	18.7	6.7	12.2	4.9	15.5
All Tests	3.8	6.0	2.8	7.0	3.3	6.5

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

A large performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (0.72) to the normalized speed of OpenJPA with PostgreSQL database server (4.6) reveals that in that case, OpenJPA with PostgreSQL server is 6.4 times faster than DataNucleus with Derby server.

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.72) to the normalized speed of DataNucleus with Derby database server (5.7) reveals that in that case, OpenJPA with PostgreSQL server is 7.9 times slower than DataNucleus with Derby server.

JPA Performance Benchmark (JPAB)