Comparison of DataNucleus with H2 server vs Hibernate 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	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server
Basic Person Test	3.4	7.1	2.2	3.4	2.8	5.2
Element Collection Test	1.2	2.9	0.64	1.7	0.92	2.3
Inheritance Test	3.0	7.0	1.9	3.6	2.4	5.3
Indexing Test	5.3	9.3	3.5	6.1	4.4	7.7
Graph (Binary Tree) Test	2.1	3.0	1.3	2.9	1.7	2.9
Multithreading Test	10.0	31.7	4.3	13.9	7.2	22.8
All Tests	4.2	10.2	2.3	5.3	3.2	7.7

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

A large performance gap has been detected when using multithreading with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (4.3) to the normalized speed of Hibernate with PostgreSQL database server (13.9) reveals that in that case, Hibernate with PostgreSQL server is 3.2 times faster 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	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server
Basic Person Test	2.5	5.5	5.2	11.5	3.9	8.5
Element Collection Test	0.56	0.025	1.1	0.017	0.82	0.021
Inheritance Test	2.2	5.2	6.1	14.0	4.2	9.6
Indexing Test	2.1	4.6	7.7	13.3	4.9	8.9
Graph (Binary Tree) Test	5.7	0.61	8.9	0.78	7.3	0.70
Multithreading Test	2.3	11.3	8.7	17.0	5.5	14.2
All Tests	2.5	4.5	6.3	9.4	4.4	7.0

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

A large performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (2.3) to the normalized speed of Hibernate with PostgreSQL database server (11.3) reveals that in that case, Hibernate with PostgreSQL server is 4.9 times faster than DataNucleus with H2 server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.017) to the normalized speed of DataNucleus with H2 database server (1.1) reveals that in that case, Hibernate with PostgreSQL server is 64.7 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	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server
Basic Person Test	4.1	55.5	1.3	6.1	2.7	30.8
Element Collection Test	4.0	11.0	0.49	0.016	2.3	5.5
Inheritance Test	2.9	52.3	1.5	8.7	2.2	30.5
Indexing Test	0.0036	0.050	1.5	8.8	0.75	4.4
Multithreading Test	1.3	55.2	failed	9.2	1.3	32.2
All Tests	2.5	34.8	1.2	6.6	1.9	20.7

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

The results above show that in general Hibernate with PostgreSQL server is much more efficient than DataNucleus with H2 server in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with H2 database server (1.9) to the normalized speed of Hibernate with PostgreSQL database server (20.7) reveals that in these tests, Hibernate with PostgreSQL server is 10.9 times faster than DataNucleus with H2 server.

A huge performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (1.3) to the normalized speed of Hibernate with PostgreSQL database server (55.2) reveals that in that case, Hibernate with PostgreSQL server is 42.5 times faster than DataNucleus with H2 server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.016) to the normalized speed of DataNucleus with H2 database server (0.49) reveals that in that case, Hibernate with PostgreSQL server is 30.6 times slower than DataNucleus with H2 server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server
Basic Person Test	2.5	5.3	1.4	2.7	1.9	4.0
Element Collection Test	2.0	0.067	1.0	0.026	1.5	0.046
Inheritance Test	2.4	5.4	2.3	3.8	2.3	4.6
Indexing Test	2.7	5.4	3.0	4.3	2.9	4.8
Graph (Binary Tree) Test	1.8	1.1	0.60	0.58	1.2	0.82
Multithreading Test	failed	29.6	failed	6.3	failed	18.0
All Tests	2.3	7.8	1.7	2.9	2.0	5.4

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

The results above show that in general Hibernate 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 Hibernate with PostgreSQL database server (5.4) reveals that in these tests, Hibernate with PostgreSQL server is 2.7 times faster than DataNucleus with H2 server.

A large performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with H2 database server (2.4) to the normalized speed of Hibernate with PostgreSQL database server (5.4) reveals that in that case, Hibernate with PostgreSQL server is 2.3 times faster than DataNucleus with H2 server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.026) to the normalized speed of DataNucleus with H2 database server (1.0) reveals that in that case, Hibernate with PostgreSQL server is 38.5 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	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server
Basic Person Test	3.4	5.3	1.3	4.2	2.3	4.8
Element Collection Test	1.5	0.020	0.68	stopped	1.1	0.0098
Inheritance Test	2.7	5.1	1.3	4.2	2.0	4.6
Indexing Test	5.7	9.5	1.9	6.3	3.8	7.9
Graph (Binary Tree) Test	1.5	0.012	1.2	0.012	1.3	0.012
Multithreading Test	failed	23.3	5.1	21.8	5.1	22.5
All Tests	3.0	7.2	1.9	6.1	2.4	6.6

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

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

A large performance gap has been detected when using multithreading with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (5.1) to the normalized speed of Hibernate with PostgreSQL database server (21.8) reveals that in that case, Hibernate with PostgreSQL server is 4.3 times faster than DataNucleus with H2 server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.012) to the normalized speed of DataNucleus with H2 database server (1.5) reveals that in that case, Hibernate with PostgreSQL server is 125 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	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server	DataNucleus H2 server	Hibernate PostgreSQL server
Basic Person Test	3.2	15.7	2.3	5.6	2.7	10.7
Element Collection Test	1.9	2.8	0.78	0.35	1.3	1.6
Inheritance Test	2.6	15.0	2.6	6.9	2.6	10.9
Indexing Test	3.2	5.8	3.5	7.8	3.3	6.8
Graph (Binary Tree) Test	2.8	1.2	3.0	1.1	2.9	1.1
Multithreading Test	4.5	30.2	6.0	13.6	5.3	21.9
All Tests	2.9	12.1	2.8	6.0	2.9	9.1

The results above show that in general Hibernate with PostgreSQL server is much 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 Hibernate with PostgreSQL database server (9.1) reveals that in these tests, Hibernate with PostgreSQL server is 3.1 times faster than DataNucleus with H2 server.

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (4.5) to the normalized speed of Hibernate with PostgreSQL database server (30.2) reveals that in that case, Hibernate with PostgreSQL server is 6.7 times faster than DataNucleus with H2 server.

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

JPA Performance Benchmark (JPAB)