• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of Hibernate with PostgreSQL server vs DataNucleus with Derby 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 Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded
Basic Person Test	7.1	4.6	3.4	2.8	5.2	3.7
Element Collection Test	2.9	2.4	1.7	1.6	2.3	2.0
Inheritance Test	7.0	4.6	3.6	2.7	5.3	3.7
Indexing Test	9.3	7.6	6.1	4.8	7.7	6.2
Graph (Binary Tree) Test	3.0	1.6	2.9	1.4	2.9	1.5
Multithreading Test	31.7	8.6	13.9	3.3	22.8	5.9
All Tests	10.2	4.9	5.3	2.8	7.7	3.8

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

A large performance gap has been detected when using multithreading with large transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (3.3) to the normalized speed of Hibernate with PostgreSQL database server (13.9) reveals that in that case, Hibernate with PostgreSQL server is 4.2 times faster than DataNucleus with Derby 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 Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded
Basic Person Test	5.5	6.8	11.5	14.9	8.5	10.9
Element Collection Test	0.025	5.4	0.017	7.6	0.021	6.5
Inheritance Test	5.2	8.8	14.0	14.8	9.6	11.8
Indexing Test	4.6	9.2	13.3	14.1	8.9	11.6
Graph (Binary Tree) Test	0.61	9.9	0.78	15.8	0.70	12.9
Multithreading Test	11.3	11.9	17.0	11.5	14.2	11.7
All Tests	4.5	8.7	9.4	13.1	7.0	10.9

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

A huge performance gap has been detected 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 embedded database (7.6) reveals that in that case, DataNucleus with Derby embedded is 447 times faster than Hibernate with PostgreSQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate PostgreSQL server	DataNucleus Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded
Basic Person Test	55.5	39.1	6.1	7.5	30.8	23.3
Element Collection Test	11.0	46.0	0.016	6.7	5.5	26.3
Inheritance Test	52.3	7.7	8.7	3.8	30.5	5.7
Indexing Test	0.050	0.053	8.8	8.0	4.4	4.0
Multithreading Test	55.2	failed	9.2	failed	32.2	failed
All Tests	34.8	23.2	6.6	6.5	20.7	14.8

DataNucleus with Derby embedded 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 embedded in executing the tested JPA queries.

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 embedded database (7.7) to the normalized speed of Hibernate with PostgreSQL database server (52.3) reveals that in that case, Hibernate with PostgreSQL server is 6.8 times faster than DataNucleus with Derby 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.016) to the normalized speed of DataNucleus with Derby embedded database (6.7) reveals that in that case, Hibernate with PostgreSQL server is 419 times slower than DataNucleus with Derby embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate PostgreSQL server	DataNucleus Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded
Basic Person Test	5.3	4.0	2.7	3.8	4.0	3.9
Element Collection Test	0.067	3.7	0.026	4.5	0.046	4.1
Inheritance Test	5.4	4.4	3.8	4.8	4.6	4.6
Indexing Test	5.4	5.2	4.3	4.2	4.8	4.7
Graph (Binary Tree) Test	1.1	2.7	0.58	1.5	0.82	2.1
Multithreading Test	29.6	failed	6.3	failed	18.0	failed
All Tests	7.8	4.0	2.9	3.7	5.4	3.9

DataNucleus with Derby embedded 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 embedded in updating JPA entity objects in the database.

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 embedded database (4.5) reveals that in that case, Hibernate with PostgreSQL server is 173 times slower than DataNucleus with Derby 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 Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded
Basic Person Test	5.3	3.5	4.2	1.3	4.8	2.4
Element Collection Test	0.020	1.9	stopped	1.6	0.0098	1.7
Inheritance Test	5.1	2.4	4.2	1.3	4.6	1.9
Indexing Test	9.5	6.6	6.3	1.9	7.9	4.3
Graph (Binary Tree) Test	0.012	0.81	0.012	0.93	0.012	0.87
Multithreading Test	23.3	failed	21.8	failed	22.5	failed
All Tests	7.2	3.0	6.1	1.4	6.6	2.2

DataNucleus with Derby embedded 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 embedded in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby embedded database (2.2) to the normalized speed of Hibernate with PostgreSQL database server (6.6) reveals that in these tests, Hibernate with PostgreSQL server is 3.0 times faster than DataNucleus with Derby embedded.

A large performance gap has been detected when using database indexes with large transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (1.9) to the normalized speed of Hibernate with PostgreSQL database server (6.3) reveals that in that case, Hibernate with PostgreSQL server is 3.3 times faster than DataNucleus with Derby embedded.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.020) to the normalized speed of DataNucleus with Derby embedded database (1.9) reveals that in that case, Hibernate with PostgreSQL server is 95.0 times slower than DataNucleus with Derby 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 Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded	Hibernate PostgreSQL server	DataNucleus Derby embedded
Basic Person Test	15.7	11.6	5.6	6.1	10.7	8.8
Element Collection Test	2.8	11.9	0.35	4.4	1.6	8.1
Inheritance Test	15.0	5.6	6.9	5.5	10.9	5.5
Indexing Test	5.8	5.7	7.8	6.6	6.8	6.2
Graph (Binary Tree) Test	1.2	3.7	1.1	4.9	1.1	4.3
Multithreading Test	30.2	10.3	13.6	7.4	21.9	8.8
All Tests	12.1	8.0	6.0	5.7	9.1	6.9

The results above show that in general Hibernate with PostgreSQL server is more efficient than DataNucleus with Derby embedded in performing JPA database operations.

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (10.3) to the normalized speed of Hibernate with PostgreSQL database server (30.2) reveals that in that case, Hibernate with PostgreSQL server is 2.9 times faster than DataNucleus with Derby 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 Derby embedded database (4.4) reveals that in that case, Hibernate with PostgreSQL server is 12.6 times slower than DataNucleus with Derby 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.