Comparison of OpenJPA with Derby server vs DataNucleus 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
	OpenJPA Derby server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server
Basic Person Test	3.1	4.1	2.7	2.6	2.9	3.3
Element Collection Test	2.0	0.91	1.7	0.38	1.8	0.64
Inheritance Test	3.0	3.8	2.3	2.4	2.6	3.1
Indexing Test	4.7	6.0	4.1	6.4	4.4	6.2
Graph (Binary Tree) Test	0.71	0.91	0.64	0.77	0.67	0.84
Multithreading Test	6.0	18.0	3.8	8.3	4.9	13.1
All Tests	3.3	5.6	2.5	3.5	2.9	4.5

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

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

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.38) to the normalized speed of OpenJPA with Derby database server (1.7) reveals that in that case, DataNucleus with PostgreSQL server is 4.5 times slower than OpenJPA 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 server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server
Basic Person Test	0.78	1.7	11.6	7.6	6.2	4.6
Element Collection Test	0.0024	0.73	1.1	0.63	0.54	0.68
Inheritance Test	0.014	1.5	5.0	9.3	2.5	5.4
Indexing Test	0.62	1.5	13.0	9.2	6.8	5.3
Graph (Binary Tree) Test	0.065	2.6	0.39	12.3	0.23	7.4
Multithreading Test	1.6	3.4	19.0	10.8	10.3	7.1
All Tests	0.51	1.9	8.4	8.3	4.4	5.1

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

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with Derby database server (0.0024) to the normalized speed of DataNucleus with PostgreSQL database server (0.73) reveals that in that case, DataNucleus with PostgreSQL server is 304 times faster than OpenJPA 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 server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server
Basic Person Test	29.2	49.1	5.5	4.7	17.3	26.9
Element Collection Test	2.2	39.1	1.4	0.48	1.8	19.8
Inheritance Test	2.2	55.9	1.0	6.6	1.6	31.2
Indexing Test	2.2	0.048	11.7	6.4	7.0	3.2
Multithreading Test	35.5	failed	8.3	failed	21.9	failed
All Tests	14.3	36.0	5.6	4.5	9.9	20.3

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

The results above show that in general DataNucleus with PostgreSQL server is more efficient than OpenJPA with Derby server in executing the tested JPA queries. Comparing the normalized speed of OpenJPA with Derby database server (9.9) to the normalized speed of DataNucleus with PostgreSQL database server (20.3) reveals that in these tests, DataNucleus with PostgreSQL server is 2.1 times faster than OpenJPA 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 OpenJPA with Derby database server (2.2) to the normalized speed of DataNucleus with PostgreSQL database server (55.9) reveals that in that case, DataNucleus with PostgreSQL server is 25.4 times faster than OpenJPA with Derby server.

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.048) to the normalized speed of OpenJPA with Derby database server (2.2) reveals that in that case, DataNucleus with PostgreSQL server is 45.8 times slower than OpenJPA 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 server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server
Basic Person Test	1.5	2.1	4.0	0.84	2.8	1.5
Element Collection Test	0.0081	1.4	1.9	0.64	0.94	1.0
Inheritance Test	0.043	2.1	3.8	1.2	1.9	1.7
Indexing Test	1.8	2.2	6.8	1.5	4.3	1.8
Graph (Binary Tree) Test	0.16	0.65	0.27	0.20	0.22	0.42
Multithreading Test	6.9	0.46	5.0	failed	5.9	0.46
All Tests	1.7	1.5	3.6	0.87	2.7	1.2

DataNucleus with PostgreSQL server has failed in 1 tests (see exceptions).

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

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.46) to the normalized speed of OpenJPA with Derby database server (6.9) reveals that in that case, OpenJPA with Derby server is 15.0 times faster than DataNucleus with PostgreSQL server.

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	OpenJPA Derby server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server
Basic Person Test	1.4	3.0	3.7	1.3	2.5	2.2
Element Collection Test	0.0082	1.0	1.4	0.39	0.71	0.69
Inheritance Test	0.035	2.8	2.5	1.3	1.3	2.1
Indexing Test	2.3	5.4	3.5	1.9	2.9	3.7
Graph (Binary Tree) Test	0.13	0.38	0.35	0.37	0.24	0.37
Multithreading Test	3.6	13.8	4.0	failed	3.8	13.8
All Tests	1.3	4.4	2.6	1.1	1.9	2.9

DataNucleus with PostgreSQL server has failed in 1 tests (see exceptions).

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (0.0082) to the normalized speed of DataNucleus with PostgreSQL database server (1.0) reveals that in that case, DataNucleus with PostgreSQL server is 122 times faster than OpenJPA with Derby server.

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.39) to the normalized speed of OpenJPA with Derby database server (1.4) reveals that in that case, DataNucleus with PostgreSQL server is 3.6 times slower than OpenJPA 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 server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server	OpenJPA Derby server	DataNucleus PostgreSQL server
Basic Person Test	7.2	12.0	5.5	3.4	6.4	7.7
Element Collection Test	0.84	8.6	1.5	0.50	1.2	4.6
Inheritance Test	1.1	13.2	2.9	4.2	2.0	8.7
Indexing Test	2.3	3.0	7.8	5.1	5.1	4.0
Graph (Binary Tree) Test	0.27	1.1	0.41	3.4	0.34	2.3
Multithreading Test	10.7	8.9	8.0	9.5	9.4	9.1
All Tests	3.9	8.0	4.5	3.8	4.2	6.0

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with Derby database server (1.1) to the normalized speed of DataNucleus with PostgreSQL database server (13.2) reveals that in that case, DataNucleus with PostgreSQL server is 12.0 times faster than OpenJPA with Derby server.

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

JPA Performance Benchmark (JPAB)