Comparison of ObjectDB embedded vs EclipseLink with HSQLDB 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
	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded
Basic Person Test	100	27.1	100	17.2	100	22.2
Element Collection Test	100	17.2	100	8.2	100	12.7
Inheritance Test	100	26.7	100	11.9	100	19.3
Indexing Test	100	30.6	100	18.6	100	24.6
Graph (Binary Tree) Test	88.4	20.0	100	15.9	94.2	18.0
Multithreading Test	100	32.5	100	11.4	100	22.0
All Tests	98.1	25.7	100	13.9	99.0	19.8

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

A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (8.2) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 12.2 times faster than EclipseLink with HSQLDB embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded
Basic Person Test	100	24.4	100	36.0	100	30.2
Element Collection Test	100	14.9	100	19.1	100	17.0
Inheritance Test	100	22.8	100	40.0	100	31.4
Indexing Test	100	20.7	100	38.7	100	29.7
Graph (Binary Tree) Test	100	8.7	100	14.2	100	11.4
Multithreading Test	100	24.2	100	28.0	100	26.1
All Tests	100	19.3	100	29.3	100	24.3

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with HSQLDB embedded in retrieving JPA entity objects from the database. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (24.3) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 4.1 times faster than EclipseLink with HSQLDB embedded.

A huge performance gap has been detected when using graphs of objects with small retrieval size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (8.7) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 11.5 times faster than EclipseLink with HSQLDB embedded.

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded
Basic Person Test	100	2.9	100	0.88	100	1.9
Element Collection Test	100	3.2	100	1.4	100	2.3
Inheritance Test	100	2.6	100	1.1	100	1.9
Indexing Test	100	21.5	100	33.3	100	27.4
Multithreading Test	100	1.1	100	0.52	100	0.82
All Tests	100	6.3	100	7.4	100	6.9

The results above show that in general ObjectDB embedded is much 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 ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 14.5 times faster than EclipseLink with HSQLDB embedded.

A huge performance gap has been detected when using multithreading with large retrieval size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (0.52) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 192 times faster 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
	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded
Basic Person Test	100	17.9	100	7.0	100	12.5
Element Collection Test	100	14.6	100	8.3	100	11.4
Inheritance Test	100	16.2	100	9.7	100	13.0
Indexing Test	100	12.0	100	6.8	100	9.4
Graph (Binary Tree) Test	100	4.7	100	3.4	100	4.0
Multithreading Test	100	24.4	100	4.4	100	14.4
All Tests	100	15.0	100	6.6	100	10.8

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with HSQLDB embedded in updating JPA entity objects in the database. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (10.8) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 9.3 times faster than EclipseLink with HSQLDB embedded.

A huge performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (3.4) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 29.4 times faster than EclipseLink with HSQLDB embedded.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded
Basic Person Test	100	32.3	100	20.3	100	26.3
Element Collection Test	100	14.3	100	6.0	100	10.2
Inheritance Test	100	29.2	100	23.9	100	26.6
Indexing Test	100	55.3	100	27.1	100	41.2
Graph (Binary Tree) Test	100	6.8	100	14.1	100	10.4
Multithreading Test	100	52.9	100	28.4	100	40.6
All Tests	100	31.8	100	20.0	100	25.9

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

A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (6.0) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 16.7 times faster than EclipseLink with HSQLDB embedded.

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded
Basic Person Test	100	41.4	100	41.4	100	41.4
Element Collection Test	100	46.9	100	46.9	100	46.9
Inheritance Test	100	41.4	100	41.4	100	41.4
Indexing Test	100	48.4	100	49.2	100	48.8
Graph (Binary Tree) Test	100	28.5	100	21.4	100	25.0
Multithreading Test	91.1	51.9	22.0	10.3	56.6	31.1
All Tests	98.5	43.1	87.0	35.1	92.8	39.1

The results above show that in general ObjectDB embedded is more efficient than EclipseLink with HSQLDB embedded in using disk space. Comparing the normalized score of EclipseLink with HSQLDB embedded database (39.1) to the normalized score of ObjectDB embedded database (92.8) reveals that in these tests, ObjectDB embedded is 2.4 times more efficient than EclipseLink with HSQLDB embedded.

A large gap has been detected when using graphs of objects with large transaction size. Comparing the normalized score of EclipseLink with HSQLDB embedded database (21.4) to the normalized score of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 4.7 times more efficient than EclipseLink with HSQLDB embedded.

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded	ObjectDB embedded	EclipseLink HSQLDB embedded
Basic Person Test	100	20.9	100	16.3	100	18.6
Element Collection Test	100	12.8	100	8.6	100	10.7
Inheritance Test	100	19.5	100	17.3	100	18.4
Indexing Test	100	28.0	100	24.9	100	26.5
Graph (Binary Tree) Test	97.1	10.0	100	11.9	98.5	11.0
Multithreading Test	100	27.0	100	14.6	100	20.8
All Tests	99.6	20.1	100	15.7	99.8	17.9

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with HSQLDB embedded in performing JPA database operations. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (17.9) to the normalized speed of ObjectDB embedded database (99.8) reveals that in these tests, ObjectDB embedded is 5.6 times faster than EclipseLink with HSQLDB embedded.

A huge performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (8.6) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 11.6 times faster than EclipseLink with HSQLDB embedded.

JPA Performance Benchmark (JPAB)