Comparison of DataNucleus with H2 server vs EclipseLink with PostgreSQL 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	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server
Basic Person Test	3.4	7.3	2.2	4.2	2.8	5.8
Element Collection Test	1.2	3.1	0.64	1.9	0.92	2.5
Inheritance Test	3.0	6.9	1.9	5.0	2.4	5.9
Indexing Test	5.3	10.0	3.5	6.8	4.4	8.4
Graph (Binary Tree) Test	2.1	3.5	1.3	3.3	1.7	3.4
Multithreading Test	10.0	31.8	4.3	14.5	7.2	23.1
All Tests	4.2	10.4	2.3	6.0	3.2	8.2

The results above show that in general EclipseLink with PostgreSQL server is more efficient than DataNucleus with H2 server in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with H2 database server (3.2) to the normalized speed of EclipseLink with PostgreSQL database server (8.2) reveals that in these tests, EclipseLink with PostgreSQL server is 2.6 times faster than DataNucleus with H2 server.

A large performance gap has been detected when using multithreading with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (4.3) to the normalized speed of EclipseLink with PostgreSQL database server (14.5) reveals that in that case, EclipseLink with PostgreSQL server is 3.4 times faster than DataNucleus with H2 server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 server	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server
Basic Person Test	2.5	6.8	5.2	17.2	3.9	12.0
Element Collection Test	0.56	0.026	1.1	0.020	0.82	0.023
Inheritance Test	2.2	6.0	6.1	19.7	4.2	12.9
Indexing Test	2.1	5.6	7.7	19.5	4.9	12.6
Graph (Binary Tree) Test	5.7	0.47	8.9	0.61	7.3	0.54
Multithreading Test	2.3	13.5	8.7	27.8	5.5	20.6
All Tests	2.5	5.4	6.3	14.1	4.4	9.8

The results above show that in general EclipseLink with PostgreSQL server is more efficient than DataNucleus with H2 server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with H2 database server (4.4) to the normalized speed of EclipseLink with PostgreSQL database server (9.8) reveals that in these tests, EclipseLink with PostgreSQL server is 2.2 times faster than DataNucleus with H2 server.

A large performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (2.3) to the normalized speed of EclipseLink with PostgreSQL database server (13.5) reveals that in that case, EclipseLink with PostgreSQL server is 5.9 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.020) to the normalized speed of DataNucleus with H2 database server (1.1) reveals that in that case, EclipseLink with PostgreSQL server is 55.0 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	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server
Basic Person Test	4.1	55.5	1.3	7.8	2.7	31.6
Element Collection Test	4.0	15.4	0.49	0.028	2.3	7.7
Inheritance Test	2.9	54.9	1.5	11.5	2.2	33.2
Indexing Test	0.0036	0.077	1.5	10.0	0.75	5.1
Multithreading Test	1.3	55.3	failed	12.0	1.3	33.7
All Tests	2.5	36.2	1.2	8.3	1.9	22.3

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

The results above show that in general EclipseLink with PostgreSQL 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 EclipseLink with PostgreSQL database server (22.3) reveals that in these tests, EclipseLink with PostgreSQL server is 11.7 times faster than DataNucleus with H2 server.

A huge performance gap has been detected when using multithreading with small retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (1.3) to the normalized speed of EclipseLink with PostgreSQL database server (55.3) reveals that in that case, EclipseLink with PostgreSQL server is 42.5 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.028) to the normalized speed of DataNucleus with H2 database server (0.49) reveals that in that case, EclipseLink with PostgreSQL server is 17.5 times slower 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	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server
Basic Person Test	2.5	6.2	1.4	4.1	1.9	5.1
Element Collection Test	2.0	0.080	1.0	0.028	1.5	0.054
Inheritance Test	2.4	6.4	2.3	6.1	2.3	6.2
Indexing Test	2.7	6.5	3.0	7.0	2.9	6.8
Graph (Binary Tree) Test	1.8	0.90	0.60	0.50	1.2	0.70
Multithreading Test	failed	36.0	failed	9.1	failed	22.5
All Tests	2.3	9.3	1.7	4.5	2.0	6.9

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

The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with H2 server in updating JPA entity objects in the database. Comparing the normalized speed of DataNucleus with H2 database server (2.0) to the normalized speed of EclipseLink with PostgreSQL database server (6.9) reveals that in these tests, EclipseLink with PostgreSQL server is 3.4 times faster than DataNucleus with H2 server.

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 EclipseLink with PostgreSQL database server (4.1) reveals that in that case, EclipseLink with PostgreSQL server is 2.9 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.028) to the normalized speed of DataNucleus with H2 database server (1.0) reveals that in that case, EclipseLink with PostgreSQL server is 35.7 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	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server
Basic Person Test	3.4	5.7	1.3	5.7	2.3	5.7
Element Collection Test	1.5	0.025	0.68	stopped	1.1	0.012
Inheritance Test	2.7	5.5	1.3	5.4	2.0	5.4
Indexing Test	5.7	10.4	1.9	10.0	3.8	10.2
Graph (Binary Tree) Test	1.5	0.016	1.2	0.013	1.3	0.015
Multithreading Test	failed	26.3	5.1	16.8	5.1	21.6
All Tests	3.0	8.0	1.9	6.3	2.4	7.2

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

The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with H2 server in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with H2 database server (2.4) to the normalized speed of EclipseLink with PostgreSQL database server (7.2) reveals that in these tests, EclipseLink with PostgreSQL server is 3.0 times faster than DataNucleus with H2 server.

A large performance gap has been detected when using database indexes with large transaction size. Comparing the normalized speed of DataNucleus with H2 database server (1.9) to the normalized speed of EclipseLink with PostgreSQL database server (10.0) reveals that in that case, EclipseLink with PostgreSQL server is 5.3 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using graphs of objects with small transaction size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.016) to the normalized speed of DataNucleus with H2 database server (1.5) reveals that in that case, EclipseLink with PostgreSQL server is 93.8 times slower than DataNucleus with H2 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	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server	DataNucleus H2 server	EclipseLink PostgreSQL server
Basic Person Test	3.2	16.3	2.3	7.8	2.7	12.1
Element Collection Test	1.9	3.7	0.78	0.40	1.3	2.1
Inheritance Test	2.6	15.9	2.6	9.5	2.6	12.7
Indexing Test	3.2	6.5	3.5	10.7	3.3	8.6
Graph (Binary Tree) Test	2.8	1.2	3.0	1.1	2.9	1.2
Multithreading Test	4.5	32.6	6.0	16.0	5.3	24.3
All Tests	2.9	13.1	2.8	7.8	2.9	10.5

The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with H2 server in performing JPA database operations. Comparing the normalized speed of DataNucleus with H2 database server (2.9) to the normalized speed of EclipseLink with PostgreSQL database server (10.5) reveals that in these tests, EclipseLink with PostgreSQL server is 3.6 times faster than DataNucleus with H2 server.

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with H2 database server (4.5) to the normalized speed of EclipseLink with PostgreSQL database server (32.6) reveals that in that case, EclipseLink with PostgreSQL server is 7.2 times faster than DataNucleus with H2 server.

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using graphs of objects with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (1.1) to the normalized speed of DataNucleus with H2 database server (3.0) reveals that in that case, EclipseLink with PostgreSQL server is 2.7 times slower than DataNucleus with H2 server.

JPA Performance Benchmark (JPAB)