• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus with Derby 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 Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server
Basic Person Test	2.8	7.1	2.3	3.4	2.6	5.2
Element Collection Test	0.71	2.9	0.35	1.7	0.53	2.3
Inheritance Test	2.7	7.0	2.0	3.6	2.3	5.3
Indexing Test	4.5	9.3	4.0	6.1	4.3	7.7
Graph (Binary Tree) Test	0.62	3.0	0.53	2.9	0.57	2.9
Multithreading Test	4.9	31.7	3.4	13.9	4.1	22.8
All Tests	2.7	10.2	2.1	5.3	2.4	7.7

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server
Basic Person Test	0.56	5.5	6.3	11.5	3.4	8.5
Element Collection Test	0.36	0.025	0.93	0.017	0.64	0.021
Inheritance Test	0.45	5.2	6.8	14.0	3.6	9.6
Indexing Test	0.50	4.6	7.1	13.3	3.8	8.9
Graph (Binary Tree) Test	0.22	0.61	6.6	0.78	3.4	0.70
Multithreading Test	1.2	11.3	10.0	17.0	5.6	14.2
All Tests	0.55	4.5	6.3	9.4	3.4	7.0

The results above show that in general Hibernate with PostgreSQL server is more efficient than DataNucleus with Derby server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby database server (3.4) to the normalized speed of Hibernate with PostgreSQL database server (7.0) reveals that in these tests, Hibernate with PostgreSQL server is 2.1 times faster than DataNucleus 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 DataNucleus with Derby database server (0.45) to the normalized speed of Hibernate with PostgreSQL database server (5.2) reveals that in that case, Hibernate with PostgreSQL server is 11.6 times faster than DataNucleus with Derby 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 Derby database server (0.93) reveals that in that case, Hibernate with PostgreSQL server is 54.7 times slower than DataNucleus with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server
Basic Person Test	37.7	55.5	3.6	6.1	20.7	30.8
Element Collection Test	25.9	11.0	1.4	0.016	13.6	5.5
Inheritance Test	6.5	52.3	1.8	8.7	4.2	30.5
Indexing Test	0.030	0.050	4.9	8.8	2.5	4.4
Multithreading Test	failed	55.2	failed	9.2	failed	32.2
All Tests	17.5	34.8	2.9	6.6	10.2	20.7

DataNucleus with Derby 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 Derby server in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with Derby database server (10.2) to the normalized speed of Hibernate with PostgreSQL database server (20.7) reveals that in these tests, Hibernate with PostgreSQL server is 2.0 times faster than DataNucleus with Derby server.

A large performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of DataNucleus with Derby database server (6.5) to the normalized speed of Hibernate with PostgreSQL database server (52.3) reveals that in that case, Hibernate with PostgreSQL server is 8.0 times faster than DataNucleus with Derby 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 Derby database server (1.4) reveals that in that case, Hibernate with PostgreSQL server is 87.5 times slower than DataNucleus with Derby server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server
Basic Person Test	1.1	5.3	0.85	2.7	0.99	4.0
Element Collection Test	0.81	0.067	0.62	0.026	0.71	0.046
Inheritance Test	1.2	5.4	1.3	3.8	1.2	4.6
Indexing Test	1.2	5.4	1.5	4.3	1.3	4.8
Graph (Binary Tree) Test	0.29	1.1	0.41	0.58	0.35	0.82
Multithreading Test	failed	29.6	failed	6.3	failed	18.0
All Tests	0.93	7.8	0.92	2.9	0.92	5.4

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

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

A large performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of DataNucleus with Derby database server (1.1) to the normalized speed of Hibernate with PostgreSQL database server (5.3) reveals that in that case, Hibernate with PostgreSQL server is 4.8 times faster than DataNucleus with Derby 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 Derby database server (0.62) reveals that in that case, Hibernate with PostgreSQL server is 23.8 times slower than DataNucleus with Derby server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server
Basic Person Test	1.3	5.3	1.3	4.2	1.3	4.8
Element Collection Test	0.61	0.020	0.33	stopped	0.47	0.0098
Inheritance Test	1.0	5.1	1.3	4.2	1.2	4.6
Indexing Test	2.3	9.5	1.9	6.3	2.1	7.9
Graph (Binary Tree) Test	0.26	0.012	0.46	0.012	0.36	0.012
Multithreading Test	failed	23.3	failed	21.8	failed	22.5
All Tests	1.1	7.2	1.1	6.1	1.1	6.6

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

The results above show that in general Hibernate with PostgreSQL server is much more efficient than DataNucleus with Derby server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby database server (1.1) to the normalized speed of Hibernate with PostgreSQL database server (6.6) reveals that in these tests, Hibernate with PostgreSQL server is 6.0 times faster than DataNucleus with Derby 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 Derby database server (1.0) to the normalized speed of Hibernate with PostgreSQL database server (5.1) reveals that in that case, Hibernate with PostgreSQL server is 5.1 times faster than DataNucleus with Derby server.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using graphs of objects with large transaction size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.012) to the normalized speed of DataNucleus with Derby database server (0.46) reveals that in that case, Hibernate with PostgreSQL server is 38.3 times slower than DataNucleus with Derby server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server	DataNucleus Derby server	Hibernate PostgreSQL server
Basic Person Test	8.7	15.7	2.9	5.6	5.8	10.7
Element Collection Test	5.7	2.8	0.72	0.35	3.2	1.6
Inheritance Test	2.4	15.0	2.6	6.9	2.5	10.9
Indexing Test	1.7	5.8	3.9	7.8	2.8	6.8
Graph (Binary Tree) Test	0.35	1.2	2.0	1.1	1.2	1.1
Multithreading Test	3.0	30.2	6.7	13.6	4.9	21.9
All Tests	3.8	12.1	2.8	6.0	3.3	9.1

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

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

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 Derby database server (0.72) reveals that in that case, Hibernate with PostgreSQL server is 2.1 times slower than DataNucleus with Derby 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.