Comparison of DataNucleus with H2 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 H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server
Basic Person Test	3.4	5.2	2.2	4.8	2.8	5.0
Element Collection Test	1.2	2.8	0.64	2.2	0.92	2.5
Inheritance Test	3.0	4.6	1.9	3.2	2.4	3.9
Indexing Test	5.3	7.4	3.5	6.9	4.4	7.1
Graph (Binary Tree) Test	2.1	0.98	1.3	0.81	1.7	0.89
Multithreading Test	10.0	23.4	4.3	9.1	7.2	16.2
All Tests	4.2	7.4	2.3	4.5	3.2	5.9

The results above show that in general OpenJPA with PostgreSQL server is more efficient than DataNucleus with H2 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 H2 database server (0.64) to the normalized speed of OpenJPA with PostgreSQL database server (2.2) reveals that in that case, OpenJPA with PostgreSQL server is 3.4 times faster than DataNucleus with H2 server.

On the other hand, OpenJPA with PostgreSQL server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of OpenJPA with PostgreSQL database server (0.98) to the normalized speed of DataNucleus with H2 database server (2.1) reveals that in that case, OpenJPA with PostgreSQL server is 2.1 times slower than DataNucleus with H2 server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server
Basic Person Test	2.5	5.8	5.2	16.1	3.9	10.9
Element Collection Test	0.56	0.013	1.1	8.7	0.82	4.4
Inheritance Test	2.2	5.2	6.1	17.6	4.2	11.4
Indexing Test	2.1	4.8	7.7	18.7	4.9	11.8
Graph (Binary Tree) Test	5.7	0.27	8.9	0.35	7.3	0.31
Multithreading Test	2.3	11.9	8.7	23.3	5.5	17.6
All Tests	2.5	4.7	6.3	14.1	4.4	9.4

The results above show that in general OpenJPA with PostgreSQL server is more efficient than DataNucleus with H2 server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with H2 database server (4.4) to the normalized speed of OpenJPA with PostgreSQL database server (9.4) reveals that in these tests, OpenJPA with PostgreSQL server is 2.1 times faster than DataNucleus with H2 server.

A large performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (1.1) to the normalized speed of OpenJPA with PostgreSQL database server (8.7) reveals that in that case, OpenJPA with PostgreSQL server is 7.9 times faster than DataNucleus with H2 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 H2 database server (0.56) reveals that in that case, OpenJPA with PostgreSQL server is 43.1 times slower than DataNucleus with H2 server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server
Basic Person Test	4.1	failed	1.3	failed	2.7	failed
Element Collection Test	4.0	failed	0.49	failed	2.3	failed
Inheritance Test	2.9	failed	1.5	failed	2.2	failed
Indexing Test	0.0036	failed	1.5	failed	0.75	failed
Multithreading Test	1.3	failed	failed	failed	1.3	failed
All Tests	2.5	failed	1.2	failed	1.9	failed

DataNucleus with H2 server has failed in 1 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 H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server
Basic Person Test	2.5	4.9	1.4	3.9	1.9	4.4
Element Collection Test	2.0	0.033	1.0	4.6	1.5	2.3
Inheritance Test	2.4	4.8	2.3	4.9	2.3	4.9
Indexing Test	2.7	5.1	3.0	6.0	2.9	5.6
Graph (Binary Tree) Test	1.8	0.57	0.60	0.31	1.2	0.44
Multithreading Test	failed	22.2	failed	7.4	failed	14.8
All Tests	2.3	6.3	1.7	4.5	2.0	5.4

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

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

A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (1.0) to the normalized speed of OpenJPA with PostgreSQL database server (4.6) reveals that in that case, OpenJPA with PostgreSQL server is 4.6 times faster than DataNucleus with H2 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 H2 database server (2.0) reveals that in that case, OpenJPA with PostgreSQL server is 60.6 times slower than DataNucleus with H2 server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server
Basic Person Test	3.4	4.6	1.3	5.3	2.3	5.0
Element Collection Test	1.5	0.032	0.68	2.8	1.1	1.4
Inheritance Test	2.7	4.3	1.3	4.6	2.0	4.4
Indexing Test	5.7	8.0	1.9	7.1	3.8	7.5
Graph (Binary Tree) Test	1.5	0.53	1.2	0.55	1.3	0.54
Multithreading Test	failed	17.4	5.1	9.1	5.1	13.3
All Tests	3.0	5.8	1.9	4.9	2.4	5.4

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

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

A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (0.68) to the normalized speed of OpenJPA with PostgreSQL database server (2.8) reveals that in that case, OpenJPA with PostgreSQL server is 4.1 times faster than DataNucleus with H2 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 H2 database server (1.5) reveals that in that case, OpenJPA with PostgreSQL server is 46.9 times slower than DataNucleus with H2 server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server	DataNucleus H2 server	OpenJPA PostgreSQL server
Basic Person Test	3.2	5.1	2.3	7.5	2.7	6.3
Element Collection Test	1.9	0.72	0.78	4.6	1.3	2.6
Inheritance Test	2.6	4.7	2.6	7.6	2.6	6.2
Indexing Test	3.2	6.3	3.5	9.7	3.3	8.0
Graph (Binary Tree) Test	2.8	0.59	3.0	0.50	2.9	0.55
Multithreading Test	4.5	18.7	6.0	12.2	5.3	15.5
All Tests	2.9	6.0	2.8	7.0	2.9	6.5

The results above show that in general OpenJPA with PostgreSQL server is more efficient than DataNucleus with H2 server in performing JPA database operations. Comparing the normalized speed of DataNucleus with H2 database server (2.9) to the normalized speed of OpenJPA with PostgreSQL database server (6.5) reveals that in these tests, OpenJPA with PostgreSQL server is 2.2 times faster than DataNucleus with H2 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 H2 database server (0.78) to the normalized speed of OpenJPA with PostgreSQL database server (4.6) reveals that in that case, OpenJPA with PostgreSQL server is 5.9 times faster than DataNucleus with H2 server.

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

JPA Performance Benchmark (JPAB)