Comparison of DataNucleus with Derby server vs Hibernate with HSQLDB 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 Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server
Basic Person Test	5.2	stopped	7.4	stopped	6.3	stopped
Element Collection Test	3.9	stopped	2.6	stopped	3.2	stopped
Inheritance Test	4.0	stopped	7.7	stopped	5.9	stopped
Indexing Test	7.2	stopped	9.9	stopped	8.5	stopped
Graph (Binary Tree) Test	2.4	stopped	2.0	stopped	2.2	stopped
Multithreading Test	6.0	stopped	0.0000	stopped	3.0	stopped
All Tests	4.8	stopped	4.9	stopped	4.9	stopped

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server
Basic Person Test	0.29	stopped	3.8	stopped	2.0	stopped
Element Collection Test	0.31	stopped	2.1	stopped	1.2	stopped
Inheritance Test	0.32	stopped	3.0	stopped	1.7	stopped
Indexing Test	0.31	stopped	3.2	stopped	1.8	stopped
Graph (Binary Tree) Test	1.2	stopped	failed	stopped	1.2	stopped
Multithreading Test	0.48	stopped	4.8	stopped	2.6	stopped
All Tests	0.49	stopped	3.4	stopped	1.8	stopped

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

The results above show that in general DataNucleus with Derby server is much more efficient than Hibernate with HSQLDB server in retrieving JPA entity objects from the database. Comparing the normalized speed of Hibernate with HSQLDB database server (0.0000) to the normalized speed of DataNucleus with Derby database server (1.8) reveals that in these tests, DataNucleus with Derby server is ? times faster than Hibernate with HSQLDB server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server
Basic Person Test	0.072	stopped	0.62	stopped	0.35	stopped
Element Collection Test	0.16	stopped	0.68	stopped	0.42	stopped
Inheritance Test	0.063	stopped	0.73	stopped	0.40	stopped
Indexing Test	0.066	stopped	0.67	stopped	0.37	stopped
Multithreading Test	0.33	stopped	failed	stopped	0.33	stopped
All Tests	0.14	stopped	0.68	stopped	0.38	stopped

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server
Basic Person Test	0.51	stopped	0.56	stopped	0.54	stopped
Element Collection Test	1.1	stopped	0.90	stopped	1.0	stopped
Inheritance Test	0.45	stopped	0.82	stopped	0.64	stopped
Indexing Test	1.9	stopped	0.81	stopped	1.4	stopped
Graph (Binary Tree) Test	0.41	stopped	failed	stopped	0.41	stopped
Multithreading Test	failed	stopped	failed	stopped	failed	stopped
All Tests	0.88	stopped	0.78	stopped	0.83	stopped

DataNucleus with Derby server 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 HSQLDB server in updating JPA entity objects in the database. Comparing the normalized speed of Hibernate with HSQLDB database server (0.0000) to the normalized speed of DataNucleus with Derby database server (0.83) reveals that in these tests, DataNucleus with Derby server is ? times faster than Hibernate with HSQLDB server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server
Basic Person Test	1.8	stopped	0.81	stopped	1.3	stopped
Element Collection Test	2.5	stopped	0.25	stopped	1.4	stopped
Inheritance Test	2.1	stopped	0.59	stopped	1.3	stopped
Indexing Test	3.4	stopped	0.57	stopped	2.0	stopped
Graph (Binary Tree) Test	3.2	stopped	failed	stopped	3.2	stopped
Multithreading Test	failed	stopped	26.7	stopped	26.7	stopped
All Tests	2.6	stopped	5.8	stopped	4.2	stopped

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

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 HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server	DataNucleus Derby server	Hibernate HSQLDB server
Basic Person Test	1.6	stopped	2.6	stopped	2.1	stopped
Element Collection Test	1.6	stopped	1.3	stopped	1.4	stopped
Inheritance Test	1.4	stopped	2.6	stopped	2.0	stopped
Indexing Test	2.6	stopped	3.0	stopped	2.8	stopped
Graph (Binary Tree) Test	1.8	stopped	2.0	stopped	1.9	stopped
Multithreading Test	2.3	stopped	10.5	stopped	6.4	stopped
All Tests	1.8	stopped	3.4	stopped	2.6	stopped

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

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

JPA Performance Benchmark (JPAB)