Comparison of DataNucleus with PostgreSQL server vs EclipseLink with Derby 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
	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	4.1	5.5	2.6	3.7	3.3	4.6
Element Collection Test	0.91	3.0	0.38	1.7	0.64	2.4
Inheritance Test	3.8	5.3	2.4	3.5	3.1	4.4
Indexing Test	6.0	6.9	6.4	4.6	6.2	5.8
Graph (Binary Tree) Test	0.91	2.0	0.77	1.9	0.84	1.9
Multithreading Test	18.0	9.3	8.3	4.1	13.1	6.7
All Tests	5.6	5.3	3.5	3.2	4.5	4.3

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

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	1.7	16.4	7.6	58.7	4.6	37.5
Element Collection Test	0.73	7.5	0.63	13.3	0.68	10.4
Inheritance Test	1.5	17.1	9.3	58.9	5.4	38.0
Indexing Test	1.5	14.2	9.2	67.4	5.3	40.8
Graph (Binary Tree) Test	2.6	2.8	12.3	5.7	7.4	4.2
Multithreading Test	3.4	28.0	10.8	48.7	7.1	38.4
All Tests	1.9	14.3	8.3	42.1	5.1	28.2

The results above show that in general EclipseLink with Derby embedded is much more efficient than DataNucleus with PostgreSQL server in retrieving JPA entity objects from the database. Comparing the normalized speed of DataNucleus with PostgreSQL database server (5.1) to the normalized speed of EclipseLink with Derby embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 5.5 times faster than DataNucleus with PostgreSQL server.

A huge performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.63) to the normalized speed of EclipseLink with Derby embedded database (13.3) reveals that in that case, EclipseLink with Derby embedded is 21.1 times faster than DataNucleus with PostgreSQL server.

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using graphs of objects with large retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (5.7) to the normalized speed of DataNucleus with PostgreSQL database server (12.3) reveals that in that case, EclipseLink with Derby embedded is 2.2 times slower than DataNucleus with PostgreSQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	49.1	53.4	4.7	13.8	26.9	33.6
Element Collection Test	39.1	37.9	0.48	4.4	19.8	21.2
Inheritance Test	55.9	37.4	6.6	15.0	31.2	26.2
Indexing Test	0.048	7.6	6.4	49.3	3.2	28.4
Multithreading Test	failed	41.2	failed	6.1	failed	23.6
All Tests	36.0	35.5	4.5	17.7	20.3	26.6

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

The results above show that in general EclipseLink with Derby embedded is more efficient than DataNucleus with PostgreSQL server in executing the tested JPA queries.

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.048) to the normalized speed of EclipseLink with Derby embedded database (7.6) reveals that in that case, EclipseLink with Derby embedded is 158 times faster than DataNucleus with PostgreSQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	2.1	6.4	0.84	6.7	1.5	6.5
Element Collection Test	1.4	5.4	0.64	6.2	1.0	5.8
Inheritance Test	2.1	6.5	1.2	9.2	1.7	7.8
Indexing Test	2.2	7.3	1.5	11.1	1.8	9.2
Graph (Binary Tree) Test	0.65	2.8	0.20	1.7	0.42	2.2
Multithreading Test	0.46	21.3	failed	5.0	0.46	13.1
All Tests	1.5	8.3	0.87	6.6	1.2	7.5

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

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

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.46) to the normalized speed of EclipseLink with Derby embedded database (21.3) reveals that in that case, EclipseLink with Derby embedded is 46.3 times faster than DataNucleus with PostgreSQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	3.0	4.6	1.3	4.7	2.2	4.6
Element Collection Test	1.0	2.5	0.39	1.4	0.69	1.9
Inheritance Test	2.8	3.9	1.3	4.5	2.1	4.2
Indexing Test	5.4	6.2	1.9	3.8	3.7	5.0
Graph (Binary Tree) Test	0.38	1.1	0.37	1.0	0.37	1.1
Multithreading Test	13.8	6.2	failed	5.8	13.8	6.0
All Tests	4.4	4.1	1.1	3.5	2.9	3.8

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

The results above show that in general EclipseLink with Derby embedded is more efficient than DataNucleus with PostgreSQL server in deleting JPA entity objects from 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 PostgreSQL database server (1.3) to the normalized speed of EclipseLink with Derby embedded database (4.7) reveals that in that case, EclipseLink with Derby embedded is 3.6 times faster than DataNucleus with PostgreSQL server.

On the other hand, EclipseLink with Derby embedded is slower, for instance, when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (6.2) to the normalized speed of DataNucleus with PostgreSQL database server (13.8) reveals that in that case, EclipseLink with Derby embedded is 2.2 times slower than DataNucleus with PostgreSQL server.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded	DataNucleus PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	12.0	17.3	3.4	17.5	7.7	17.4
Element Collection Test	8.6	11.3	0.50	5.4	4.6	8.3
Inheritance Test	13.2	14.0	4.2	18.2	8.7	16.1
Indexing Test	3.0	8.4	5.1	27.2	4.0	17.8
Graph (Binary Tree) Test	1.1	2.2	3.4	2.6	2.3	2.4
Multithreading Test	8.9	21.2	9.5	13.9	9.1	17.6
All Tests	8.0	12.7	3.8	14.5	6.0	13.6

The results above show that in general EclipseLink with Derby embedded is more efficient than DataNucleus with PostgreSQL server in performing JPA database operations. Comparing the normalized speed of DataNucleus with PostgreSQL database server (6.0) to the normalized speed of EclipseLink with Derby embedded database (13.6) reveals that in these tests, EclipseLink with Derby embedded is 2.3 times faster than DataNucleus with PostgreSQL server.

A huge performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.50) to the normalized speed of EclipseLink with Derby embedded database (5.4) reveals that in that case, EclipseLink with Derby embedded is 10.8 times faster than DataNucleus with PostgreSQL server.

JPA Performance Benchmark (JPAB)