Comparison of EclipseLink with MySQL server vs ObjectDB 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 MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded
Basic Person Test	3.6	100	1.5	100	2.6	100
Element Collection Test	1.5	100	0.69	100	1.1	100
Inheritance Test	3.5	100	1.4	100	2.4	100
Indexing Test	5.3	100	2.5	100	3.9	100
Graph (Binary Tree) Test	1.7	88.4	1.3	100	1.5	94.2
Multithreading Test	7.2	100	2.4	100	4.8	100
All Tests	3.8	98.1	1.6	100	2.7	99.0

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded
Basic Person Test	0.43	100	15.5	100	8.0	100
Element Collection Test	0.16	100	1.4	100	0.78	100
Inheritance Test	0.39	100	17.6	100	9.0	100
Indexing Test	0.43	100	16.6	100	8.5	100
Graph (Binary Tree) Test	0.53	100	0.76	100	0.65	100
Multithreading Test	0.19	100	11.0	100	5.6	100
All Tests	0.35	100	10.5	100	5.4	100

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

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

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

Retrieval Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded
Basic Person Test	1.5	100	0.44	100	0.95	100
Element Collection Test	1.4	100	0.43	100	0.92	100
Inheritance Test	1.1	100	0.61	100	0.86	100
Indexing Test	0.26	100	0.52	100	0.39	100
Multithreading Test	1.9	100	0.72	100	1.3	100
All Tests	1.2	100	0.54	100	0.88	100

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

A huge performance gap has been detected when using database indexes with small retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.26) to the normalized speed of ObjectDB embedded database (100) reveals that in that case, ObjectDB embedded is 385 times faster than EclipseLink with MySQL server.

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded
Basic Person Test	0.39	100	1.8	100	1.1	100
Element Collection Test	0.23	100	1.4	100	0.83	100
Inheritance Test	0.42	100	2.6	100	1.5	100
Indexing Test	0.46	100	3.1	100	1.8	100
Graph (Binary Tree) Test	0.67	100	0.41	100	0.54	100
Multithreading Test	0.48	100	2.6	100	1.5	100
All Tests	0.44	100	2.0	100	1.2	100

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

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

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

Transaction Size =>	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded
Basic Person Test	0.35	100	1.7	100	1.0	100
Element Collection Test	0.11	100	0.51	100	0.31	100
Inheritance Test	0.29	100	1.6	100	0.94	100
Indexing Test	0.46	100	1.9	100	1.2	100
Graph (Binary Tree) Test	0.54	100	0.49	100	0.51	100
Multithreading Test	0.31	100	3.6	100	1.9	100
All Tests	0.34	100	1.6	100	0.98	100

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

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

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

Transaction/Retrieval Size	Few Entities		Many Entities		Average Score
	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded	EclipseLink MySQL server	ObjectDB embedded
Basic Person Test	1.3	100	4.2	100	2.7	100
Element Collection Test	0.69	100	0.89	100	0.79	100
Inheritance Test	1.1	100	4.8	100	2.9	100
Indexing Test	1.4	100	4.9	100	3.2	100
Graph (Binary Tree) Test	0.85	97.1	0.73	100	0.79	98.5
Multithreading Test	2.0	100	4.0	100	3.0	100
All Tests	1.2	99.6	3.3	100	2.3	99.8

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

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

JPA Performance Benchmark (JPAB)