• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of DataNucleus with DB4O embedded 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 DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded
Basic Person Test	0.059	0.083	1.3	1.0	0.69	0.55
Element Collection Test	0.045	0.067	1.0	0.69	0.52	0.38
Inheritance Test	0.051	0.080	0.85	0.99	0.45	0.54
Indexing Test	0.080	0.098	2.3	1.0	1.2	0.55
Graph (Binary Tree) Test	failed	0.27	failed	0.96	failed	0.61
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.059	0.12	1.4	0.93	0.71	0.53

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

The results above show that in general DataNucleus with DB4O embedded is more efficient than Hibernate with SQLite embedded in persisting JPA entity objects to the database.

A large performance gap has been detected when using database indexes with large transaction size. Comparing the normalized speed of Hibernate with SQLite embedded database (1.0) to the normalized speed of DataNucleus with DB4O embedded database (2.3) reveals that in that case, DataNucleus with DB4O embedded is 2.3 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 DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded
Basic Person Test	0.0047	1.8	1.8	1.3	0.90	1.5
Element Collection Test	0.0038	0.0008	1.5	failed	0.77	0.0008
Inheritance Test	0.0035	2.4	2.2	1.4	1.1	1.9
Indexing Test	0.0043	1.9	1.8	2.3	0.89	2.1
Graph (Binary Tree) Test	failed	0.56	failed	0.88	failed	0.72
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.0041	1.3	1.8	1.5	0.91	1.4

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

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

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 SQLite embedded database (2.4) reveals that in that case, Hibernate with SQLite embedded is 686 times faster than DataNucleus with DB4O embedded.

On the other hand, Hibernate with SQLite embedded is slower, for instance, 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 DB4O embedded database (0.0038) reveals that in that case, Hibernate with SQLite embedded is 4.8 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
	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded
Basic Person Test	failed	1.1	failed	0.22	failed	0.65
Element Collection Test	failed	0.39	failed	failed	failed	0.39
Inheritance Test	failed	0.53	failed	0.28	failed	0.40
Indexing Test	failed	0.0011	failed	0.43	failed	0.21
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	failed	0.50	failed	0.31	failed	0.42

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded
Basic Person Test	0.012	0.076	0.76	0.65	0.39	0.37
Element Collection Test	0.012	0.0022	1.1	failed	0.53	0.0022
Inheritance Test	0.011	0.079	0.81	0.97	0.41	0.53
Indexing Test	0.011	0.057	1.3	0.54	0.64	0.30
Graph (Binary Tree) Test	failed	0.26	failed	0.42	failed	0.34
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.012	0.094	0.97	0.65	0.49	0.34

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

The results above show that in general DataNucleus with DB4O embedded is more efficient than Hibernate with SQLite embedded in updating JPA entity objects in the database.

A large 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 DB4O embedded database (0.012) reveals that in that case, DataNucleus with DB4O embedded is 5.5 times faster than Hibernate with SQLite embedded.

On the other hand, DataNucleus with DB4O embedded is slower, for instance, 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 SQLite embedded database (0.079) reveals that in that case, DataNucleus with DB4O embedded is 7.2 times slower 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 DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded
Basic Person Test	0.011	0.061	1.5	0.91	0.74	0.49
Element Collection Test	0.010	0.0007	1.6	failed	0.80	0.0007
Inheritance Test	0.0093	0.058	1.1	0.90	0.57	0.48
Indexing Test	0.017	0.079	2.1	0.54	1.1	0.31
Graph (Binary Tree) Test	failed	0.24	failed	0.80	failed	0.52
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.012	0.088	1.6	0.79	0.79	0.40

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

The results above show that in general DataNucleus with DB4O embedded is more efficient than Hibernate with SQLite embedded in deleting JPA entity objects from the database.

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 DB4O embedded database (0.010) reveals that in that case, DataNucleus with DB4O embedded is 14.3 times faster than Hibernate with SQLite embedded.

On the other hand, DataNucleus with DB4O embedded is slower, for instance, when using class inheritance in the object model with small transaction size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.0093) to the normalized speed of Hibernate with SQLite embedded database (0.058) reveals that in that case, DataNucleus with DB4O embedded is 6.2 times slower than Hibernate with SQLite embedded.

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded
Basic Person Test	35.1	90.2	35.4	90.2	35.2	90.2
Element Collection Test	29.5	82.0	29.9	82.0	29.7	82.0
Inheritance Test	33.4	80.5	33.5	80.5	33.4	80.5
Indexing Test	41.0	93.4	41.9	94.8	41.5	94.1
Graph (Binary Tree) Test	failed	67.9	failed	50.9	failed	59.4
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	34.8	82.8	35.2	79.7	35.0	81.2

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

The results above show that in general Hibernate with SQLite embedded is more efficient than DataNucleus with DB4O embedded in using disk space. Comparing the normalized score of DataNucleus with DB4O embedded database (35.0) to the normalized score of Hibernate with SQLite embedded database (81.2) reveals that in these tests, Hibernate with SQLite embedded is 2.3 times more efficient than DataNucleus with DB4O embedded.

A large gap has been detected when using JPA element collections with small transaction size. Comparing the normalized score of DataNucleus with DB4O embedded database (29.5) to the normalized score of Hibernate with SQLite embedded database (82.0) reveals that in that case, Hibernate with SQLite embedded is 2.8 times more efficient 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
	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded	DataNucleus DB4O embedded	Hibernate SQLite embedded
Basic Person Test	0.022	0.63	1.3	0.81	0.68	0.72
Element Collection Test	0.018	0.092	1.3	0.69	0.66	0.19
Inheritance Test	0.019	0.63	1.2	0.91	0.63	0.77
Indexing Test	0.028	0.42	1.9	0.96	0.94	0.69
Graph (Binary Tree) Test	failed	0.33	failed	0.77	failed	0.55
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.022	0.42	1.4	0.86	0.73	0.62

The results above show that in general DataNucleus with DB4O embedded is slightly more efficient than Hibernate with SQLite embedded in performing JPA database operations.

On the other hand, DataNucleus with DB4O embedded is slower, for instance, 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 SQLite embedded database (0.63) reveals that in that case, DataNucleus with DB4O embedded is 33.2 times slower 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.