Comparison of Hibernate with Derby embedded 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
	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server
Basic Person Test	5.9	4.1	3.8	2.6	4.9	3.3
Element Collection Test	2.9	0.91	1.8	0.38	2.3	0.64
Inheritance Test	5.3	3.8	3.7	2.4	4.5	3.1
Indexing Test	7.0	6.0	4.8	6.4	5.9	6.2
Graph (Binary Tree) Test	1.9	0.91	1.7	0.77	1.8	0.84
Multithreading Test	10.5	18.0	3.7	8.3	7.1	13.1
All Tests	5.6	5.6	3.3	3.5	4.4	4.5

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

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

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.38) to the normalized speed of Hibernate with Derby embedded database (1.8) reveals that in that case, DataNucleus with PostgreSQL server is 4.7 times slower than Hibernate with Derby embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server
Basic Person Test	14.2	1.7	16.4	7.6	15.3	4.6
Element Collection Test	4.4	0.73	4.9	0.63	4.6	0.68
Inheritance Test	10.3	1.5	18.6	9.3	14.4	5.4
Indexing Test	10.0	1.5	16.4	9.2	13.2	5.3
Graph (Binary Tree) Test	2.6	2.6	3.0	12.3	2.8	7.4
Multithreading Test	19.3	3.4	19.3	10.8	19.3	7.1
All Tests	10.1	1.9	13.1	8.3	11.6	5.1

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

A large performance gap has been detected when using simple basic entities with small retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (1.7) to the normalized speed of Hibernate with Derby embedded database (14.2) reveals that in that case, Hibernate with Derby embedded is 8.4 times faster than DataNucleus with PostgreSQL server.

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server
Basic Person Test	49.3	49.1	6.8	4.7	28.1	26.9
Element Collection Test	37.6	39.1	2.7	0.48	20.1	19.8
Inheritance Test	24.1	55.9	7.6	6.6	15.9	31.2
Indexing Test	5.3	0.048	14.8	6.4	10.1	3.2
Multithreading Test	39.7	failed	6.1	failed	22.9	failed
All Tests	31.2	36.0	7.6	4.5	19.4	20.3

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

The results above show that in general DataNucleus with PostgreSQL server is slightly more efficient than Hibernate 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 Hibernate with Derby embedded database (24.1) to the normalized speed of DataNucleus with PostgreSQL database server (55.9) reveals that in that case, DataNucleus with PostgreSQL server is 2.3 times faster than Hibernate with Derby embedded.

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.048) to the normalized speed of Hibernate with Derby embedded database (5.3) reveals that in that case, DataNucleus with PostgreSQL server is 110 times slower than Hibernate with Derby embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server
Basic Person Test	4.5	2.1	3.2	0.84	3.8	1.5
Element Collection Test	3.9	1.4	3.1	0.64	3.5	1.0
Inheritance Test	4.6	2.1	4.5	1.2	4.5	1.7
Indexing Test	4.6	2.2	5.5	1.5	5.1	1.8
Graph (Binary Tree) Test	2.7	0.65	1.2	0.20	2.0	0.42
Multithreading Test	11.6	0.46	2.6	failed	7.1	0.46
All Tests	5.3	1.5	3.3	0.87	4.3	1.2

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

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

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.46) to the normalized speed of Hibernate with Derby embedded database (11.6) reveals that in that case, Hibernate with Derby embedded is 25.2 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
	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server
Basic Person Test	3.8	3.0	4.2	1.3	4.0	2.2
Element Collection Test	2.3	1.0	1.5	0.39	1.9	0.69
Inheritance Test	4.0	2.8	4.3	1.3	4.2	2.1
Indexing Test	5.5	5.4	3.6	1.9	4.6	3.7
Graph (Binary Tree) Test	0.74	0.38	0.96	0.37	0.85	0.37
Multithreading Test	5.6	13.8	4.9	failed	5.3	13.8
All Tests	3.7	4.4	3.3	1.1	3.5	2.9

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

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

A large performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.39) to the normalized speed of Hibernate with Derby embedded database (1.5) reveals that in that case, Hibernate with Derby embedded is 3.8 times faster than DataNucleus with PostgreSQL server.

On the other hand, Hibernate with Derby embedded is slower, for instance, when using multithreading with small transaction size. Comparing the normalized speed of Hibernate with Derby embedded database (5.6) to the normalized speed of DataNucleus with PostgreSQL database server (13.8) reveals that in that case, Hibernate with Derby embedded is 2.5 times slower than DataNucleus with PostgreSQL server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server	Hibernate Derby embedded	DataNucleus PostgreSQL server
Basic Person Test	15.5	12.0	6.9	3.4	11.2	7.7
Element Collection Test	10.2	8.6	2.8	0.50	6.5	4.6
Inheritance Test	9.7	13.2	7.7	4.2	8.7	8.7
Indexing Test	6.5	3.0	9.0	5.1	7.8	4.0
Graph (Binary Tree) Test	2.0	1.1	1.7	3.4	1.8	2.3
Multithreading Test	17.3	8.9	7.3	9.5	12.3	9.1
All Tests	10.5	8.0	6.1	3.8	8.3	6.0

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

A large performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.50) to the normalized speed of Hibernate with Derby embedded database (2.8) reveals that in that case, Hibernate with Derby embedded is 5.6 times faster than DataNucleus with PostgreSQL server.

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

JPA Performance Benchmark (JPAB)