Comparison of EclipseLink 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
	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	7.3	5.5	4.2	3.7	5.8	4.6
Element Collection Test	3.1	3.0	1.9	1.7	2.5	2.4
Inheritance Test	6.9	5.3	5.0	3.5	5.9	4.4
Indexing Test	10.0	6.9	6.8	4.6	8.4	5.8
Graph (Binary Tree) Test	3.5	2.0	3.3	1.9	3.4	1.9
Multithreading Test	31.8	9.3	14.5	4.1	23.1	6.7
All Tests	10.4	5.3	6.0	3.2	8.2	4.3

The results above show that in general EclipseLink with PostgreSQL server is 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 EclipseLink with PostgreSQL database server (14.5) reveals that in that case, EclipseLink with PostgreSQL server is 3.5 times faster 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
	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	6.8	16.4	17.2	58.7	12.0	37.5
Element Collection Test	0.026	7.5	0.020	13.3	0.023	10.4
Inheritance Test	6.0	17.1	19.7	58.9	12.9	38.0
Indexing Test	5.6	14.2	19.5	67.4	12.6	40.8
Graph (Binary Tree) Test	0.47	2.8	0.61	5.7	0.54	4.2
Multithreading Test	13.5	28.0	27.8	48.7	20.6	38.4
All Tests	5.4	14.3	14.1	42.1	9.8	28.2

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

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 EclipseLink with Derby embedded database (13.3) reveals that in that case, EclipseLink with Derby embedded is 665 times faster 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	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	55.5	53.4	7.8	13.8	31.6	33.6
Element Collection Test	15.4	37.9	0.028	4.4	7.7	21.2
Inheritance Test	54.9	37.4	11.5	15.0	33.2	26.2
Indexing Test	0.077	7.6	10.0	49.3	5.1	28.4
Multithreading Test	55.3	41.2	12.0	6.1	33.7	23.6
All Tests	36.2	35.5	8.3	17.7	22.3	26.6

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

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.028) to the normalized speed of EclipseLink with Derby embedded database (4.4) reveals that in that case, EclipseLink with Derby embedded is 157 times faster than EclipseLink with PostgreSQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	6.2	6.4	4.1	6.7	5.1	6.5
Element Collection Test	0.080	5.4	0.028	6.2	0.054	5.8
Inheritance Test	6.4	6.5	6.1	9.2	6.2	7.8
Indexing Test	6.5	7.3	7.0	11.1	6.8	9.2
Graph (Binary Tree) Test	0.90	2.8	0.50	1.7	0.70	2.2
Multithreading Test	36.0	21.3	9.1	5.0	22.5	13.1
All Tests	9.3	8.3	4.5	6.6	6.9	7.5

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	5.7	4.6	5.7	4.7	5.7	4.6
Element Collection Test	0.025	2.5	stopped	1.4	0.012	1.9
Inheritance Test	5.5	3.9	5.4	4.5	5.4	4.2
Indexing Test	10.4	6.2	10.0	3.8	10.2	5.0
Graph (Binary Tree) Test	0.016	1.1	0.013	1.0	0.015	1.1
Multithreading Test	26.3	6.2	16.8	5.8	21.6	6.0
All Tests	8.0	4.1	6.3	3.5	7.2	3.8

The results above show that in general EclipseLink with PostgreSQL server is more efficient than EclipseLink with Derby embedded in deleting JPA entity objects from the database.

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

On the other hand, EclipseLink with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of EclipseLink with PostgreSQL database server (0.025) to the normalized speed of EclipseLink with Derby embedded database (2.5) reveals that in that case, EclipseLink with PostgreSQL server is 100 times slower than EclipseLink with Derby 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	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded	EclipseLink PostgreSQL server	EclipseLink Derby embedded
Basic Person Test	16.3	17.3	7.8	17.5	12.1	17.4
Element Collection Test	3.7	11.3	0.40	5.4	2.1	8.3
Inheritance Test	15.9	14.0	9.5	18.2	12.7	16.1
Indexing Test	6.5	8.4	10.7	27.2	8.6	17.8
Graph (Binary Tree) Test	1.2	2.2	1.1	2.6	1.2	2.4
Multithreading Test	32.6	21.2	16.0	13.9	24.3	17.6
All Tests	13.1	12.7	7.8	14.5	10.5	13.6

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

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

JPA Performance Benchmark (JPAB)