Comparison of DataNucleus with DB4O embedded vs DataNucleus with Derby 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 DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server
Basic Person Test	0.059	2.8	1.3	2.3	0.69	2.6
Element Collection Test	0.045	0.71	1.0	0.35	0.52	0.53
Inheritance Test	0.051	2.7	0.85	2.0	0.45	2.3
Indexing Test	0.080	4.5	2.3	4.0	1.2	4.3
Graph (Binary Tree) Test	failed	0.62	failed	0.53	failed	0.57
Multithreading Test	failed	4.9	failed	3.4	failed	4.1
All Tests	0.059	2.7	1.4	2.1	0.71	2.4

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

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

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server
Basic Person Test	0.0047	0.56	1.8	6.3	0.90	3.4
Element Collection Test	0.0038	0.36	1.5	0.93	0.77	0.64
Inheritance Test	0.0035	0.45	2.2	6.8	1.1	3.6
Indexing Test	0.0043	0.50	1.8	7.1	0.89	3.8
Graph (Binary Tree) Test	failed	0.22	failed	6.6	failed	3.4
Multithreading Test	failed	1.2	failed	10.0	failed	5.6
All Tests	0.0041	0.55	1.8	6.3	0.91	3.4

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

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

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 DataNucleus with Derby database server (0.45) reveals that in that case, DataNucleus with Derby server is 129 times faster 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	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server
Basic Person Test	failed	37.7	failed	3.6	failed	20.7
Element Collection Test	failed	25.9	failed	1.4	failed	13.6
Inheritance Test	failed	6.5	failed	1.8	failed	4.2
Indexing Test	failed	0.030	failed	4.9	failed	2.5
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	failed	17.5	failed	2.9	failed	10.2

DataNucleus with DB4O embedded has failed in 10 tests (see exceptions). DataNucleus with Derby server has failed in 2 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	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server
Basic Person Test	0.012	1.1	0.76	0.85	0.39	0.99
Element Collection Test	0.012	0.81	1.1	0.62	0.53	0.71
Inheritance Test	0.011	1.2	0.81	1.3	0.41	1.2
Indexing Test	0.011	1.2	1.3	1.5	0.64	1.3
Graph (Binary Tree) Test	failed	0.29	failed	0.41	failed	0.35
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.012	0.93	0.97	0.92	0.49	0.92

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

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server
Basic Person Test	0.011	1.3	1.5	1.3	0.74	1.3
Element Collection Test	0.010	0.61	1.6	0.33	0.80	0.47
Inheritance Test	0.0093	1.0	1.1	1.3	0.57	1.2
Indexing Test	0.017	2.3	2.1	1.9	1.1	2.1
Graph (Binary Tree) Test	failed	0.26	failed	0.46	failed	0.36
Multithreading Test	failed	failed	failed	failed	failed	failed
All Tests	0.012	1.1	1.6	1.1	0.79	1.1

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

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

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

On the other hand, DataNucleus with Derby server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with Derby database server (0.33) to the normalized speed of DataNucleus with DB4O embedded database (1.6) reveals that in that case, DataNucleus with Derby server is 4.8 times slower 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	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server	DataNucleus DB4O embedded	DataNucleus Derby server
Basic Person Test	0.022	8.7	1.3	2.9	0.68	5.8
Element Collection Test	0.018	5.7	1.3	0.72	0.66	3.2
Inheritance Test	0.019	2.4	1.2	2.6	0.63	2.5
Indexing Test	0.028	1.7	1.9	3.9	0.94	2.8
Graph (Binary Tree) Test	failed	0.35	failed	2.0	failed	1.2
Multithreading Test	failed	3.0	failed	6.7	failed	4.9
All Tests	0.022	3.8	1.4	2.8	0.73	3.3

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

A huge performance gap has been detected when using simple basic entities with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with DB4O embedded database (0.022) to the normalized speed of DataNucleus with Derby database server (8.7) reveals that in that case, DataNucleus with Derby server is 395 times faster than DataNucleus with DB4O embedded.

JPA Performance Benchmark (JPAB)