Comparison of DataNucleus with H2 embedded 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 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server
Basic Person Test	19.2	7.3	8.0	4.2	13.6	5.8
Element Collection Test	6.6	3.1	2.8	1.9	4.7	2.5
Inheritance Test	15.6	6.9	4.4	5.0	10.0	5.9
Indexing Test	24.4	10.0	11.8	6.8	18.1	8.4
Graph (Binary Tree) Test	9.2	3.5	6.2	3.3	7.7	3.4
Multithreading Test	34.9	31.8	7.1	14.5	21.0	23.1
All Tests	18.3	10.4	6.7	6.0	12.5	8.2

The results above show that in general DataNucleus with H2 embedded is more efficient than EclipseLink with PostgreSQL server in persisting JPA entity objects to the database.

A large performance gap has been detected when using simple basic entities with small transaction size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (7.3) to the normalized speed of DataNucleus with H2 embedded database (19.2) reveals that in that case, DataNucleus with H2 embedded is 2.6 times faster than EclipseLink with PostgreSQL server.

On the other hand, DataNucleus with H2 embedded is slower, for instance, when using multithreading with large transaction size. Comparing the normalized speed of DataNucleus with H2 embedded database (7.1) to the normalized speed of EclipseLink with PostgreSQL database server (14.5) reveals that in that case, DataNucleus with H2 embedded is 2.0 times slower than EclipseLink with PostgreSQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server
Basic Person Test	13.2	6.8	13.5	17.2	13.3	12.0
Element Collection Test	6.4	0.026	8.9	0.020	7.7	0.023
Inheritance Test	12.2	6.0	12.7	19.7	12.4	12.9
Indexing Test	8.1	5.6	16.5	19.5	12.3	12.6
Graph (Binary Tree) Test	10.6	0.47	20.9	0.61	15.8	0.54
Multithreading Test	13.3	13.5	9.9	27.8	11.6	20.6
All Tests	10.6	5.4	13.7	14.1	12.2	9.8

The results above show that in general DataNucleus with H2 embedded is slightly more efficient than EclipseLink with PostgreSQL server in retrieving JPA entity objects from the database.

A huge performance gap has been detected 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 embedded database (8.9) reveals that in that case, DataNucleus with H2 embedded is 445 times faster than EclipseLink with PostgreSQL server.

On the other hand, DataNucleus with H2 embedded is slower, for instance, when using multithreading with large retrieval size. Comparing the normalized speed of DataNucleus with H2 embedded database (9.9) to the normalized speed of EclipseLink with PostgreSQL database server (27.8) reveals that in that case, DataNucleus with H2 embedded is 2.8 times slower than EclipseLink with PostgreSQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server
Basic Person Test	4.7	55.5	1.4	7.8	3.1	31.6
Element Collection Test	5.0	15.4	2.4	0.028	3.7	7.7
Inheritance Test	3.8	54.9	1.6	11.5	2.7	33.2
Indexing Test	0.0041	0.077	1.8	10.0	0.91	5.1
Multithreading Test	1.2	55.3	0.79	12.0	1.0	33.7
All Tests	3.0	36.2	1.6	8.3	2.3	22.3

The results above show that in general EclipseLink with PostgreSQL server is much more efficient than DataNucleus with H2 embedded in executing the tested JPA queries. Comparing the normalized speed of DataNucleus with H2 embedded database (2.3) to the normalized speed of EclipseLink with PostgreSQL database server (22.3) reveals that in these tests, EclipseLink with PostgreSQL server is 9.7 times faster than DataNucleus with H2 embedded.

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

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 embedded database (2.4) reveals that in that case, EclipseLink with PostgreSQL server is 85.7 times slower than DataNucleus with H2 embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server
Basic Person Test	10.0	6.2	3.9	4.1	6.9	5.1
Element Collection Test	7.6	0.080	3.9	0.028	5.8	0.054
Inheritance Test	9.4	6.4	4.4	6.1	6.9	6.2
Indexing Test	10.6	6.5	5.9	7.0	8.2	6.8
Graph (Binary Tree) Test	5.9	0.90	3.7	0.50	4.8	0.70
Multithreading Test	failed	36.0	failed	9.1	failed	22.5
All Tests	8.7	9.3	4.4	4.5	6.5	6.9

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

The results above show that in general EclipseLink with PostgreSQL server is slightly more efficient than DataNucleus with H2 embedded in updating JPA entity objects in the database.

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 embedded database (3.9) reveals that in that case, EclipseLink with PostgreSQL server is 139 times slower than DataNucleus with H2 embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server
Basic Person Test	4.2	5.7	1.3	5.7	2.8	5.7
Element Collection Test	4.9	0.025	1.6	stopped	3.2	0.012
Inheritance Test	4.0	5.5	1.3	5.4	2.7	5.4
Indexing Test	7.5	10.4	1.9	10.0	4.7	10.2
Graph (Binary Tree) Test	5.6	0.016	4.1	0.013	4.8	0.015
Multithreading Test	failed	26.3	failed	16.8	failed	21.6
All Tests	5.2	8.0	2.0	6.3	3.6	7.2

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

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

A large performance gap has been detected when using database indexes with large transaction size. Comparing the normalized speed of DataNucleus with H2 embedded database (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 embedded.

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 embedded database (5.6) reveals that in that case, EclipseLink with PostgreSQL server is 350 times slower than DataNucleus with H2 embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server
Basic Person Test	10.3	16.3	5.6	7.8	7.9	12.1
Element Collection Test	6.1	3.7	3.9	0.40	5.0	2.1
Inheritance Test	9.0	15.9	4.9	9.5	6.9	12.7
Indexing Test	10.1	6.5	7.6	10.7	8.9	8.6
Graph (Binary Tree) Test	7.8	1.2	8.7	1.1	8.3	1.2
Multithreading Test	16.5	32.6	5.9	16.0	11.2	24.3
All Tests	9.6	13.1	6.0	7.8	7.8	10.5

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

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

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.40) to the normalized speed of DataNucleus with H2 embedded database (3.9) reveals that in that case, EclipseLink with PostgreSQL server is 9.8 times slower than DataNucleus with H2 embedded.

JPA Performance Benchmark (JPAB)