• Benchmark
• Results
• Comparison

JPA Performance Benchmark (JPAB)

Comparison of EclipseLink with HSQLDB embedded vs DataNucleus 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
	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server
Basic Person Test	27.1	4.1	17.2	2.6	22.2	3.3
Element Collection Test	17.2	0.91	8.2	0.38	12.7	0.64
Inheritance Test	26.7	3.8	11.9	2.4	19.3	3.1
Indexing Test	30.6	6.0	18.6	6.4	24.6	6.2
Graph (Binary Tree) Test	20.0	0.91	15.9	0.77	18.0	0.84
Multithreading Test	32.5	18.0	11.4	8.3	22.0	13.1
All Tests	25.7	5.6	13.9	3.5	19.8	4.5

The results above show that in general EclipseLink with HSQLDB embedded is much more efficient than DataNucleus with PostgreSQL server in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with PostgreSQL database server (4.5) to the normalized speed of EclipseLink with HSQLDB embedded database (19.8) reveals that in these tests, EclipseLink with HSQLDB embedded is 4.4 times faster than DataNucleus with PostgreSQL server.

A huge performance gap has been detected when using graphs of objects with small transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.91) to the normalized speed of EclipseLink with HSQLDB embedded database (20.0) reveals that in that case, EclipseLink with HSQLDB embedded is 22.0 times faster than DataNucleus with PostgreSQL server.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server
Basic Person Test	24.4	1.7	36.0	7.6	30.2	4.6
Element Collection Test	14.9	0.73	19.1	0.63	17.0	0.68
Inheritance Test	22.8	1.5	40.0	9.3	31.4	5.4
Indexing Test	20.7	1.5	38.7	9.2	29.7	5.3
Graph (Binary Tree) Test	8.7	2.6	14.2	12.3	11.4	7.4
Multithreading Test	24.2	3.4	28.0	10.8	26.1	7.1
All Tests	19.3	1.9	29.3	8.3	24.3	5.1

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (24.3) reveals that in these tests, EclipseLink with HSQLDB embedded is 4.8 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 HSQLDB embedded database (19.1) reveals that in that case, EclipseLink with HSQLDB embedded is 30.3 times faster 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
	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server
Basic Person Test	2.9	49.1	0.88	4.7	1.9	26.9
Element Collection Test	3.2	39.1	1.4	0.48	2.3	19.8
Inheritance Test	2.6	55.9	1.1	6.6	1.9	31.2
Indexing Test	21.5	0.048	33.3	6.4	27.4	3.2
Multithreading Test	1.1	failed	0.52	failed	0.82	failed
All Tests	6.3	36.0	7.4	4.5	6.9	20.3

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

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

A huge performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (2.6) to the normalized speed of DataNucleus with PostgreSQL database server (55.9) reveals that in that case, DataNucleus with PostgreSQL server is 21.5 times faster than EclipseLink with HSQLDB embedded.

On the other hand, DataNucleus with PostgreSQL server is slower, for instance, 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 HSQLDB embedded database (21.5) reveals that in that case, DataNucleus with PostgreSQL server is 448 times slower than EclipseLink with HSQLDB embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server
Basic Person Test	17.9	2.1	7.0	0.84	12.5	1.5
Element Collection Test	14.6	1.4	8.3	0.64	11.4	1.0
Inheritance Test	16.2	2.1	9.7	1.2	13.0	1.7
Indexing Test	12.0	2.2	6.8	1.5	9.4	1.8
Graph (Binary Tree) Test	4.7	0.65	3.4	0.20	4.0	0.42
Multithreading Test	24.4	0.46	4.4	failed	14.4	0.46
All Tests	15.0	1.5	6.6	0.87	10.8	1.2

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

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (10.8) reveals that in these tests, EclipseLink with HSQLDB embedded is 9.0 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 HSQLDB embedded database (24.4) reveals that in that case, EclipseLink with HSQLDB embedded is 53.0 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
	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server
Basic Person Test	32.3	3.0	20.3	1.3	26.3	2.2
Element Collection Test	14.3	1.0	6.0	0.39	10.2	0.69
Inheritance Test	29.2	2.8	23.9	1.3	26.6	2.1
Indexing Test	55.3	5.4	27.1	1.9	41.2	3.7
Graph (Binary Tree) Test	6.8	0.38	14.1	0.37	10.4	0.37
Multithreading Test	52.9	13.8	28.4	failed	40.6	13.8
All Tests	31.8	4.4	20.0	1.1	25.9	2.9

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

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

A huge performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of DataNucleus with PostgreSQL database server (0.37) to the normalized speed of EclipseLink with HSQLDB embedded database (14.1) reveals that in that case, EclipseLink with HSQLDB embedded is 38.1 times faster 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
	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server	EclipseLink HSQLDB embedded	DataNucleus PostgreSQL server
Basic Person Test	20.9	12.0	16.3	3.4	18.6	7.7
Element Collection Test	12.8	8.6	8.6	0.50	10.7	4.6
Inheritance Test	19.5	13.2	17.3	4.2	18.4	8.7
Indexing Test	28.0	3.0	24.9	5.1	26.5	4.0
Graph (Binary Tree) Test	10.0	1.1	11.9	3.4	11.0	2.3
Multithreading Test	27.0	8.9	14.6	9.5	20.8	9.1
All Tests	20.1	8.0	15.7	3.8	17.9	6.0

The results above show that in general EclipseLink with HSQLDB 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 HSQLDB embedded database (17.9) reveals that in these tests, EclipseLink with HSQLDB embedded is 3.0 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 HSQLDB embedded database (8.6) reveals that in that case, EclipseLink with HSQLDB embedded is 17.2 times faster than DataNucleus with PostgreSQL server.

Other Head to Head DBMS/JPA Comparisons

JPA Performance Benchmark - Copyright © 2010, 2011, 2012 ObjectDB Software Ltd. - All rights reserved.
The benchmark program is released as open source under the GPL license.