• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus with Derby server vs Hibernate with SQLite 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
	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded
Basic Person Test	2.8	0.083	2.3	1.0	2.6	0.55
Element Collection Test	0.71	0.067	0.35	0.69	0.53	0.38
Inheritance Test	2.7	0.080	2.0	0.99	2.3	0.54
Indexing Test	4.5	0.098	4.0	1.0	4.3	0.55
Graph (Binary Tree) Test	0.62	0.27	0.53	0.96	0.57	0.61
Multithreading Test	4.9	failed	3.4	failed	4.1	failed
All Tests	2.7	0.12	2.1	0.93	2.4	0.53

Hibernate with SQLite embedded has failed in 2 tests (see exceptions).

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

A huge performance gap has been detected when using database indexes with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.098) to the normalized speed of DataNucleus with Derby database server (4.5) reveals that in that case, DataNucleus with Derby server is 45.9 times faster than Hibernate with SQLite embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded
Basic Person Test	0.56	1.8	6.3	1.3	3.4	1.5
Element Collection Test	0.36	0.0008	0.93	failed	0.64	0.0008
Inheritance Test	0.45	2.4	6.8	1.4	3.6	1.9
Indexing Test	0.50	1.9	7.1	2.3	3.8	2.1
Graph (Binary Tree) Test	0.22	0.56	6.6	0.88	3.4	0.72
Multithreading Test	1.2	failed	10.0	failed	5.6	failed
All Tests	0.55	1.3	6.3	1.5	3.4	1.4

Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

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

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0008) to the normalized speed of DataNucleus with Derby database server (0.36) reveals that in that case, DataNucleus with Derby server is 450 times faster than Hibernate with SQLite embedded.

On the other hand, DataNucleus with Derby server is slower, for instance, 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 SQLite embedded database (2.4) reveals that in that case, DataNucleus with Derby server is 5.3 times slower than Hibernate with SQLite embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded
Basic Person Test	37.7	1.1	3.6	0.22	20.7	0.65
Element Collection Test	25.9	0.39	1.4	failed	13.6	0.39
Inheritance Test	6.5	0.53	1.8	0.28	4.2	0.40
Indexing Test	0.030	0.0011	4.9	0.43	2.5	0.21
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	17.5	0.50	2.9	0.31	10.2	0.42

DataNucleus with Derby server has failed in 2 tests (see exceptions). Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general DataNucleus with Derby server is much more efficient than Hibernate with SQLite embedded in executing the tested JPA queries. Comparing the normalized speed of Hibernate with SQLite embedded database (0.42) to the normalized speed of DataNucleus with Derby database server (10.2) reveals that in these tests, DataNucleus with Derby server is 24.3 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using JPA element collections with small retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.39) to the normalized speed of DataNucleus with Derby database server (25.9) reveals that in that case, DataNucleus with Derby server is 66.4 times faster than Hibernate with SQLite embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded
Basic Person Test	1.1	0.076	0.85	0.65	0.99	0.37
Element Collection Test	0.81	0.0022	0.62	failed	0.71	0.0022
Inheritance Test	1.2	0.079	1.3	0.97	1.2	0.53
Indexing Test	1.2	0.057	1.5	0.54	1.3	0.30
Graph (Binary Tree) Test	0.29	0.26	0.41	0.42	0.35	0.34
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.93	0.094	0.92	0.65	0.92	0.34

DataNucleus with Derby server has failed in 2 tests (see exceptions). Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

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

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0022) to the normalized speed of DataNucleus with Derby database server (0.81) reveals that in that case, DataNucleus with Derby server is 368 times faster than Hibernate with SQLite embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded
Basic Person Test	1.3	0.061	1.3	0.91	1.3	0.49
Element Collection Test	0.61	0.0007	0.33	failed	0.47	0.0007
Inheritance Test	1.0	0.058	1.3	0.90	1.2	0.48
Indexing Test	2.3	0.079	1.9	0.54	2.1	0.31
Graph (Binary Tree) Test	0.26	0.24	0.46	0.80	0.36	0.52
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	1.1	0.088	1.1	0.79	1.1	0.40

DataNucleus with Derby server has failed in 2 tests (see exceptions). Hibernate with SQLite embedded has failed in 3 tests (see exceptions).

The results above show that in general DataNucleus with Derby server is more efficient than Hibernate with SQLite embedded in deleting JPA entity objects from the database. Comparing the normalized speed of Hibernate with SQLite embedded database (0.40) to the normalized speed of DataNucleus with Derby database server (1.1) reveals that in these tests, DataNucleus with Derby server is 2.8 times faster than Hibernate with SQLite embedded.

A huge performance gap has been detected when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.0007) to the normalized speed of DataNucleus with Derby database server (0.61) reveals that in that case, DataNucleus with Derby server is 871 times faster than Hibernate with SQLite embedded.

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 SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded	DataNucleus Derby server	Hibernate SQLite embedded
Basic Person Test	8.7	0.63	2.9	0.81	5.8	0.72
Element Collection Test	5.7	0.092	0.72	0.69	3.2	0.19
Inheritance Test	2.4	0.63	2.6	0.91	2.5	0.77
Indexing Test	1.7	0.42	3.9	0.96	2.8	0.69
Graph (Binary Tree) Test	0.35	0.33	2.0	0.77	1.2	0.55
Multithreading Test	3.0	failed	6.7	failed	4.9	failed
All Tests	3.8	0.42	2.8	0.86	3.3	0.62

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

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of Hibernate with SQLite embedded database (0.092) to the normalized speed of DataNucleus with Derby database server (5.7) reveals that in that case, DataNucleus with Derby server is 62.0 times faster than Hibernate with SQLite 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.