• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of Hibernate with PostgreSQL server vs DataNucleus with DB4O embedded

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
	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded
Basic Person Test	7.1	0.059	3.4	1.3	5.2	0.69
Element Collection Test	2.9	0.045	1.7	1.0	2.3	0.52
Inheritance Test	7.0	0.051	3.6	0.85	5.3	0.45
Indexing Test	9.3	0.080	6.1	2.3	7.7	1.2
Graph (Binary Tree) Test	3.0	failed	2.9	failed	2.9	failed
Multithreading Test	31.7	failed	13.9	failed	22.8	failed
All Tests	10.2	0.059	5.3	1.4	7.7	0.71

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.051) to the normalized speed of Hibernate with PostgreSQL database server (7.0) reveals that in that case, Hibernate with PostgreSQL server is 137 times faster than DataNucleus with DB4O embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded
Basic Person Test	5.5	0.0047	11.5	1.8	8.5	0.90
Element Collection Test	0.025	0.0038	0.017	1.5	0.021	0.77
Inheritance Test	5.2	0.0035	14.0	2.2	9.6	1.1
Indexing Test	4.6	0.0043	13.3	1.8	8.9	0.89
Graph (Binary Tree) Test	0.61	failed	0.78	failed	0.70	failed
Multithreading Test	11.3	failed	17.0	failed	14.2	failed
All Tests	4.5	0.0041	9.4	1.8	7.0	0.91

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general Hibernate with PostgreSQL server is much more efficient than DataNucleus with DB4O embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.91) to the normalized speed of Hibernate with PostgreSQL database server (7.0) reveals that in these tests, Hibernate with PostgreSQL server is 7.7 times faster than DataNucleus with DB4O embedded.

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 DB4O embedded database (0.0035) to the normalized speed of Hibernate with PostgreSQL database server (5.2) reveals that in that case, Hibernate with PostgreSQL server is 1,486 times faster than DataNucleus with DB4O embedded.

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 DB4O embedded database (1.5) reveals that in that case, Hibernate with PostgreSQL server is 88.2 times slower than DataNucleus with DB4O embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded
Basic Person Test	55.5	failed	6.1	failed	30.8	failed
Element Collection Test	11.0	failed	0.016	failed	5.5	failed
Inheritance Test	52.3	failed	8.7	failed	30.5	failed
Indexing Test	0.050	failed	8.8	failed	4.4	failed
Multithreading Test	55.2	failed	9.2	failed	32.2	failed
All Tests	34.8	failed	6.6	failed	20.7	failed

DataNucleus with DB4O embedded 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
	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded
Basic Person Test	5.3	0.012	2.7	0.76	4.0	0.39
Element Collection Test	0.067	0.012	0.026	1.1	0.046	0.53
Inheritance Test	5.4	0.011	3.8	0.81	4.6	0.41
Indexing Test	5.4	0.011	4.3	1.3	4.8	0.64
Graph (Binary Tree) Test	1.1	failed	0.58	failed	0.82	failed
Multithreading Test	29.6	failed	6.3	failed	18.0	failed
All Tests	7.8	0.012	2.9	0.97	5.4	0.49

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general Hibernate with PostgreSQL server is much more efficient than DataNucleus with DB4O embedded in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.49) to the normalized speed of Hibernate with PostgreSQL database server (5.4) reveals that in these tests, Hibernate with PostgreSQL server is 11.0 times faster than DataNucleus with DB4O embedded.

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

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 DB4O embedded database (1.1) reveals that in that case, Hibernate with PostgreSQL server is 42.3 times slower than DataNucleus with DB4O embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded
Basic Person Test	5.3	0.011	4.2	1.5	4.8	0.74
Element Collection Test	0.020	0.010	stopped	1.6	0.0098	0.80
Inheritance Test	5.1	0.0093	4.2	1.1	4.6	0.57
Indexing Test	9.5	0.017	6.3	2.1	7.9	1.1
Graph (Binary Tree) Test	0.012	failed	0.012	failed	0.012	failed
Multithreading Test	23.3	failed	21.8	failed	22.5	failed
All Tests	7.2	0.012	6.1	1.6	6.6	0.79

DataNucleus with DB4O embedded has failed in 4 tests (see exceptions).

The results above show that in general Hibernate with PostgreSQL server is much more efficient than DataNucleus with DB4O embedded in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.79) to the normalized speed of Hibernate with PostgreSQL database server (6.6) reveals that in these tests, Hibernate with PostgreSQL server is 8.4 times faster than DataNucleus with DB4O embedded.

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.017) to the normalized speed of Hibernate with PostgreSQL database server (9.5) reveals that in that case, Hibernate with PostgreSQL server is 559 times faster than DataNucleus with DB4O embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded	Hibernate PostgreSQL server	DataNucleus DB4O embedded
Basic Person Test	15.7	0.022	5.6	1.3	10.7	0.68
Element Collection Test	2.8	0.018	0.35	1.3	1.6	0.66
Inheritance Test	15.0	0.019	6.9	1.2	10.9	0.63
Indexing Test	5.8	0.028	7.8	1.9	6.8	0.94
Graph (Binary Tree) Test	1.2	failed	1.1	failed	1.1	failed
Multithreading Test	30.2	failed	13.6	failed	21.9	failed
All Tests	12.1	0.022	6.0	1.4	9.1	0.73

The results above show that in general Hibernate with PostgreSQL server is much more efficient than DataNucleus with DB4O embedded in performing JPA database operations. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.73) to the normalized speed of Hibernate with PostgreSQL database server (9.1) reveals that in these tests, Hibernate with PostgreSQL server is 12.5 times faster than DataNucleus with DB4O embedded.

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 DataNucleus with DB4O embedded database (0.019) to the normalized speed of Hibernate with PostgreSQL database server (15.0) reveals that in that case, Hibernate with PostgreSQL server is 789 times faster than DataNucleus with DB4O embedded.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.35) to the normalized speed of DataNucleus with DB4O embedded database (1.3) reveals that in that case, Hibernate with PostgreSQL server is 3.7 times slower than DataNucleus with DB4O embedded.

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.