• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus with H2 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
	DataNucleus H2 server	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server
Basic Person Test	3.4	4.1	2.2	2.6	2.8	3.3
Element Collection Test	1.2	0.91	0.64	0.38	0.92	0.64
Inheritance Test	3.0	3.8	1.9	2.4	2.4	3.1
Indexing Test	5.3	6.0	3.5	6.4	4.4	6.2
Graph (Binary Tree) Test	2.1	0.91	1.3	0.77	1.7	0.84
Multithreading Test	10.0	18.0	4.3	8.3	7.2	13.1
All Tests	4.2	5.6	2.3	3.5	3.2	4.5

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

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.91) to the normalized speed of DataNucleus with H2 database server (2.1) reveals that in that case, DataNucleus with PostgreSQL server is 2.3 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	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server
Basic Person Test	2.5	1.7	5.2	7.6	3.9	4.6
Element Collection Test	0.56	0.73	1.1	0.63	0.82	0.68
Inheritance Test	2.2	1.5	6.1	9.3	4.2	5.4
Indexing Test	2.1	1.5	7.7	9.2	4.9	5.3
Graph (Binary Tree) Test	5.7	2.6	8.9	12.3	7.3	7.4
Multithreading Test	2.3	3.4	8.7	10.8	5.5	7.1
All Tests	2.5	1.9	6.3	8.3	4.4	5.1

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

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using graphs of objects with small retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (2.6) to the normalized speed of DataNucleus with H2 database server (5.7) reveals that in that case, DataNucleus with PostgreSQL server is 2.2 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	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server
Basic Person Test	4.1	49.1	1.3	4.7	2.7	26.9
Element Collection Test	4.0	39.1	0.49	0.48	2.3	19.8
Inheritance Test	2.9	55.9	1.5	6.6	2.2	31.2
Indexing Test	0.0036	0.048	1.5	6.4	0.75	3.2
Multithreading Test	1.3	failed	failed	failed	1.3	failed
All Tests	2.5	36.0	1.2	4.5	1.9	20.3

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

The results above show that in general DataNucleus 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 DataNucleus with PostgreSQL database server (20.3) reveals that in these tests, DataNucleus with PostgreSQL server is 10.7 times faster than DataNucleus with H2 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 H2 database server (2.9) to the normalized speed of DataNucleus with PostgreSQL database server (55.9) reveals that in that case, DataNucleus with PostgreSQL server is 19.3 times faster 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	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server
Basic Person Test	2.5	2.1	1.4	0.84	1.9	1.5
Element Collection Test	2.0	1.4	1.0	0.64	1.5	1.0
Inheritance Test	2.4	2.1	2.3	1.2	2.3	1.7
Indexing Test	2.7	2.2	3.0	1.5	2.9	1.8
Graph (Binary Tree) Test	1.8	0.65	0.60	0.20	1.2	0.42
Multithreading Test	failed	0.46	failed	failed	failed	0.46
All Tests	2.3	1.5	1.7	0.87	2.0	1.2

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

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

A large performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.20) to the normalized speed of DataNucleus with H2 database server (0.60) reveals that in that case, DataNucleus with H2 server is 3.0 times faster 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
	DataNucleus H2 server	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server
Basic Person Test	3.4	3.0	1.3	1.3	2.3	2.2
Element Collection Test	1.5	1.0	0.68	0.39	1.1	0.69
Inheritance Test	2.7	2.8	1.3	1.3	2.0	2.1
Indexing Test	5.7	5.4	1.9	1.9	3.8	3.7
Graph (Binary Tree) Test	1.5	0.38	1.2	0.37	1.3	0.37
Multithreading Test	failed	13.8	5.1	failed	5.1	13.8
All Tests	3.0	4.4	1.9	1.1	2.4	2.9

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

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

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.38) to the normalized speed of DataNucleus with H2 database server (1.5) reveals that in that case, DataNucleus with PostgreSQL server is 3.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	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server	DataNucleus H2 server	DataNucleus PostgreSQL server
Basic Person Test	3.2	12.0	2.3	3.4	2.7	7.7
Element Collection Test	1.9	8.6	0.78	0.50	1.3	4.6
Inheritance Test	2.6	13.2	2.6	4.2	2.6	8.7
Indexing Test	3.2	3.0	3.5	5.1	3.3	4.0
Graph (Binary Tree) Test	2.8	1.1	3.0	3.4	2.9	2.3
Multithreading Test	4.5	8.9	6.0	9.5	5.3	9.1
All Tests	2.9	8.0	2.8	3.8	2.9	6.0

The results above show that in general DataNucleus 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 DataNucleus with PostgreSQL database server (6.0) reveals that in these tests, DataNucleus with PostgreSQL server is 2.1 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/retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (2.6) to the normalized speed of DataNucleus with PostgreSQL database server (13.2) reveals that in that case, DataNucleus with PostgreSQL server is 5.1 times faster than DataNucleus with H2 server.

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (1.1) to the normalized speed of DataNucleus with H2 database server (2.8) reveals that in that case, DataNucleus with PostgreSQL server is 2.5 times slower than DataNucleus with H2 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.