Comparison of ObjectDB embedded 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
	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded
Basic Person Test	100	5.5	100	3.7	100	4.6
Element Collection Test	100	3.0	100	1.7	100	2.4
Inheritance Test	100	5.3	100	3.5	100	4.4
Indexing Test	100	6.9	100	4.6	100	5.8
Graph (Binary Tree) Test	88.4	2.0	100	1.9	94.2	1.9
Multithreading Test	100	9.3	100	4.1	100	6.7
All Tests	98.1	5.3	100	3.2	99.0	4.3

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

A huge performance gap has been detected when using JPA element collections with large transaction size. Comparing the normalized speed of EclipseLink with Derby embedded database (1.7) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 58.8 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
	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded
Basic Person Test	100	16.4	100	58.7	100	37.5
Element Collection Test	100	7.5	100	13.3	100	10.4
Inheritance Test	100	17.1	100	58.9	100	38.0
Indexing Test	100	14.2	100	67.4	100	40.8
Graph (Binary Tree) Test	100	2.8	100	5.7	100	4.2
Multithreading Test	100	28.0	100	48.7	100	38.4
All Tests	100	14.3	100	42.1	100	28.2

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded
Basic Person Test	100	53.4	100	13.8	100	33.6
Element Collection Test	100	37.9	100	4.4	100	21.2
Inheritance Test	100	37.4	100	15.0	100	26.2
Indexing Test	100	7.6	100	49.3	100	28.4
Multithreading Test	100	41.2	100	6.1	100	23.6
All Tests	100	35.5	100	17.7	100	26.6

The results above show that in general ObjectDB embedded is much more efficient than EclipseLink with Derby embedded in executing the tested JPA queries. Comparing the normalized speed of EclipseLink with Derby embedded database (26.6) to the normalized speed of ObjectDB embedded database (100) reveals that in these tests, ObjectDB embedded is 3.8 times faster than EclipseLink with Derby embedded.

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded
Basic Person Test	100	6.4	100	6.7	100	6.5
Element Collection Test	100	5.4	100	6.2	100	5.8
Inheritance Test	100	6.5	100	9.2	100	7.8
Indexing Test	100	7.3	100	11.1	100	9.2
Graph (Binary Tree) Test	100	2.8	100	1.7	100	2.2
Multithreading Test	100	21.3	100	5.0	100	13.1
All Tests	100	8.3	100	6.6	100	7.5

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded
Basic Person Test	100	4.6	100	4.7	100	4.6
Element Collection Test	100	2.5	100	1.4	100	1.9
Inheritance Test	100	3.9	100	4.5	100	4.2
Indexing Test	100	6.2	100	3.8	100	5.0
Graph (Binary Tree) Test	100	1.1	100	1.0	100	1.1
Multithreading Test	100	6.2	100	5.8	100	6.0
All Tests	100	4.1	100	3.5	100	3.8

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded
Basic Person Test	100	51.1	100	51.0	100	51.1
Element Collection Test	100	38.5	100	39.4	100	38.9
Inheritance Test	100	48.0	100	47.9	100	48.0
Indexing Test	100	51.6	100	52.3	100	52.0
Graph (Binary Tree) Test	100	13.4	100	11.7	100	12.6
Multithreading Test	91.1	52.6	22.0	8.4	56.6	30.5
All Tests	98.5	42.5	87.0	35.1	92.8	38.8

The results above show that in general ObjectDB embedded is more efficient than EclipseLink with Derby embedded in using disk space. Comparing the normalized score of EclipseLink with Derby embedded database (38.8) 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 Derby embedded.

A large gap has been detected when using graphs of objects with large transaction size. Comparing the normalized score of EclipseLink with Derby embedded database (11.7) to the normalized score of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 8.5 times more efficient 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
	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded	ObjectDB embedded	EclipseLink Derby embedded
Basic Person Test	100	17.3	100	17.5	100	17.4
Element Collection Test	100	11.3	100	5.4	100	8.3
Inheritance Test	100	14.0	100	18.2	100	16.1
Indexing Test	100	8.4	100	27.2	100	17.8
Graph (Binary Tree) Test	97.1	2.2	100	2.6	98.5	2.4
Multithreading Test	100	21.2	100	13.9	100	17.6
All Tests	99.6	12.7	100	14.5	99.8	13.6

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

A huge performance gap has been detected when using graphs of objects with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with Derby embedded database (2.2) to the normalized speed of ObjectDB embedded database (97.1) reveals that in that case, ObjectDB embedded is 44.1 times faster than EclipseLink with Derby embedded.

JPA Performance Benchmark (JPAB)