Comparison of EclipseLink with PostgreSQL server vs DataNucleus with H2 embedded

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

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

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
	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded
Basic Person Test	55.5	4.7	7.8	1.4	31.6	3.1
Element Collection Test	15.4	5.0	0.028	2.4	7.7	3.7
Inheritance Test	54.9	3.8	11.5	1.6	33.2	2.7
Indexing Test	0.077	0.0041	10.0	1.8	5.1	0.91
Multithreading Test	55.3	1.2	12.0	0.79	33.7	1.0
All Tests	36.2	3.0	8.3	1.6	22.3	2.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
	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded
Basic Person Test	6.2	10.0	4.1	3.9	5.1	6.9
Element Collection Test	0.080	7.6	0.028	3.9	0.054	5.8
Inheritance Test	6.4	9.4	6.1	4.4	6.2	6.9
Indexing Test	6.5	10.6	7.0	5.9	6.8	8.2
Graph (Binary Tree) Test	0.90	5.9	0.50	3.7	0.70	4.8
Multithreading Test	36.0	failed	9.1	failed	22.5	failed
All Tests	9.3	8.7	4.5	4.4	6.9	6.5

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
	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded
Basic Person Test	5.7	4.2	5.7	1.3	5.7	2.8
Element Collection Test	0.025	4.9	stopped	1.6	0.012	3.2
Inheritance Test	5.5	4.0	5.4	1.3	5.4	2.7
Indexing Test	10.4	7.5	10.0	1.9	10.2	4.7
Graph (Binary Tree) Test	0.016	5.6	0.013	4.1	0.015	4.8
Multithreading Test	26.3	failed	16.8	failed	21.6	failed
All Tests	8.0	5.2	6.3	2.0	7.2	3.6

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
	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded	EclipseLink PostgreSQL server	DataNucleus H2 embedded
Basic Person Test	16.3	10.3	7.8	5.6	12.1	7.9
Element Collection Test	3.7	6.1	0.40	3.9	2.1	5.0
Inheritance Test	15.9	9.0	9.5	4.9	12.7	6.9
Indexing Test	6.5	10.1	10.7	7.6	8.6	8.9
Graph (Binary Tree) Test	1.2	7.8	1.1	8.7	1.2	8.3
Multithreading Test	32.6	16.5	16.0	5.9	24.3	11.2
All Tests	13.1	9.6	7.8	6.0	10.5	7.8

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)