Comparison of DataNucleus with H2 server vs OpenJPA 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 H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server
Basic Person Test	3.4	3.1	2.2	2.7	2.8	2.9
Element Collection Test	1.2	2.0	0.64	1.7	0.92	1.8
Inheritance Test	3.0	3.0	1.9	2.3	2.4	2.6
Indexing Test	5.3	4.7	3.5	4.1	4.4	4.4
Graph (Binary Tree) Test	2.1	0.71	1.3	0.64	1.7	0.67
Multithreading Test	10.0	6.0	4.3	3.8	7.2	4.9
All Tests	4.2	3.3	2.3	2.5	3.2	2.9

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

A large performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (0.71) to the normalized speed of DataNucleus with H2 database server (2.1) reveals that in that case, DataNucleus with H2 server is 3.0 times faster than OpenJPA with Derby server.

On the other hand, DataNucleus with H2 server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (0.64) to the normalized speed of OpenJPA with Derby database server (1.7) reveals that in that case, DataNucleus with H2 server is 2.7 times slower than OpenJPA with Derby server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server
Basic Person Test	2.5	0.78	5.2	11.6	3.9	6.2
Element Collection Test	0.56	0.0024	1.1	1.1	0.82	0.54
Inheritance Test	2.2	0.014	6.1	5.0	4.2	2.5
Indexing Test	2.1	0.62	7.7	13.0	4.9	6.8
Graph (Binary Tree) Test	5.7	0.065	8.9	0.39	7.3	0.23
Multithreading Test	2.3	1.6	8.7	19.0	5.5	10.3
All Tests	2.5	0.51	6.3	8.4	4.4	4.4

The results above show that in general OpenJPA with Derby server is equivalent to DataNucleus with H2 server in retrieving JPA entity objects from the database.

A large performance gap has been detected when using simple basic entities with large retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (5.2) to the normalized speed of OpenJPA with Derby database server (11.6) reveals that in that case, OpenJPA with Derby server is 2.2 times faster than DataNucleus with H2 server.

On the other hand, OpenJPA with Derby server is slower, for instance, when using JPA element collections with small retrieval size. Comparing the normalized speed of OpenJPA with Derby database server (0.0024) to the normalized speed of DataNucleus with H2 database server (0.56) reveals that in that case, OpenJPA with Derby server is 233 times slower than DataNucleus with H2 server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server
Basic Person Test	4.1	29.2	1.3	5.5	2.7	17.3
Element Collection Test	4.0	2.2	0.49	1.4	2.3	1.8
Inheritance Test	2.9	2.2	1.5	1.0	2.2	1.6
Indexing Test	0.0036	2.2	1.5	11.7	0.75	7.0
Multithreading Test	1.3	35.5	failed	8.3	1.3	21.9
All Tests	2.5	14.3	1.2	5.6	1.9	9.9

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

The results above show that in general OpenJPA with Derby server is much more efficient than DataNucleus with H2 server in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with H2 database server (1.9) to the normalized speed of OpenJPA with Derby database server (9.9) reveals that in these tests, OpenJPA with Derby server is 5.2 times faster than DataNucleus with H2 server.

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (0.0036) to the normalized speed of OpenJPA with Derby database server (2.2) reveals that in that case, OpenJPA with Derby server is 611 times faster than DataNucleus with H2 server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server
Basic Person Test	2.5	1.5	1.4	4.0	1.9	2.8
Element Collection Test	2.0	0.0081	1.0	1.9	1.5	0.94
Inheritance Test	2.4	0.043	2.3	3.8	2.3	1.9
Indexing Test	2.7	1.8	3.0	6.8	2.9	4.3
Graph (Binary Tree) Test	1.8	0.16	0.60	0.27	1.2	0.22
Multithreading Test	failed	6.9	failed	5.0	failed	5.9
All Tests	2.3	1.7	1.7	3.6	2.0	2.7

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

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

A large performance gap has been detected when using simple basic entities with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (1.4) to the normalized speed of OpenJPA with Derby database server (4.0) reveals that in that case, OpenJPA with Derby server is 2.9 times faster than DataNucleus with H2 server.

On the other hand, OpenJPA with Derby server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of OpenJPA with Derby database server (0.0081) to the normalized speed of DataNucleus with H2 database server (2.0) reveals that in that case, OpenJPA with Derby server is 247 times slower than DataNucleus with H2 server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server
Basic Person Test	3.4	1.4	1.3	3.7	2.3	2.5
Element Collection Test	1.5	0.0082	0.68	1.4	1.1	0.71
Inheritance Test	2.7	0.035	1.3	2.5	2.0	1.3
Indexing Test	5.7	2.3	1.9	3.5	3.8	2.9
Graph (Binary Tree) Test	1.5	0.13	1.2	0.35	1.3	0.24
Multithreading Test	failed	3.6	5.1	4.0	5.1	3.8
All Tests	3.0	1.3	1.9	2.6	2.4	1.9

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

The results above show that in general DataNucleus with H2 server is slightly more efficient than OpenJPA with Derby server 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 OpenJPA with Derby database server (0.0082) to the normalized speed of DataNucleus with H2 database server (1.5) reveals that in that case, DataNucleus with H2 server is 183 times faster than OpenJPA with Derby server.

On the other hand, DataNucleus with H2 server is slower, for instance, when using simple basic entities with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (1.3) to the normalized speed of OpenJPA with Derby database server (3.7) reveals that in that case, DataNucleus with H2 server is 2.8 times slower than OpenJPA with Derby server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server	DataNucleus H2 server	OpenJPA Derby server
Basic Person Test	3.2	7.2	2.3	5.5	2.7	6.4
Element Collection Test	1.9	0.84	0.78	1.5	1.3	1.2
Inheritance Test	2.6	1.1	2.6	2.9	2.6	2.0
Indexing Test	3.2	2.3	3.5	7.8	3.3	5.1
Graph (Binary Tree) Test	2.8	0.27	3.0	0.41	2.9	0.34
Multithreading Test	4.5	10.7	6.0	8.0	5.3	9.4
All Tests	2.9	3.9	2.8	4.5	2.9	4.2

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

A large performance gap has been detected when using simple basic entities with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (2.3) to the normalized speed of OpenJPA with Derby database server (5.5) reveals that in that case, OpenJPA with Derby server is 2.4 times faster than DataNucleus with H2 server.

On the other hand, OpenJPA with Derby server is slower, for instance, when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of OpenJPA with Derby database server (0.27) to the normalized speed of DataNucleus with H2 database server (2.8) reveals that in that case, OpenJPA with Derby server is 10.4 times slower than DataNucleus with H2 server.

JPA Performance Benchmark (JPAB)