Compare with

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 EntitiesMany EntitiesAverage Score
 EclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embedded
Basic Person Test3.61001.51002.6100
Element Collection Test1.51000.691001.1100
Inheritance Test3.51001.41002.4100
Indexing Test5.31002.51003.9100
Graph (Binary Tree) Test1.788.41.31001.594.2
Multithreading Test7.21002.41004.8100
All Tests3.898.11.61002.799.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 EntitiesMany EntitiesAverage Score
 EclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embedded
Basic Person Test0.4310015.51008.0100
Element Collection Test0.161001.41000.78100
Inheritance Test0.3910017.61009.0100
Indexing Test0.4310016.61008.5100
Graph (Binary Tree) Test0.531000.761000.65100
Multithreading Test0.1910011.01005.6100
All Tests0.3510010.51005.4100

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 EntitiesMany EntitiesAverage Score
 EclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embedded
Basic Person Test1.51000.441000.95100
Element Collection Test1.41000.431000.92100
Inheritance Test1.11000.611000.86100
Indexing Test0.261000.521000.39100
Multithreading Test1.91000.721001.3100
All Tests1.21000.541000.88100

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 EntitiesMany EntitiesAverage Score
 EclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embedded
Basic Person Test0.391001.81001.1100
Element Collection Test0.231001.41000.83100
Inheritance Test0.421002.61001.5100
Indexing Test0.461003.11001.8100
Graph (Binary Tree) Test0.671000.411000.54100
Multithreading Test0.481002.61001.5100
All Tests0.441002.01001.2100

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 EntitiesMany EntitiesAverage Score
 EclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embedded
Basic Person Test0.351001.71001.0100
Element Collection Test0.111000.511000.31100
Inheritance Test0.291001.61000.94100
Indexing Test0.461001.91001.2100
Graph (Binary Tree) Test0.541000.491000.51100
Multithreading Test0.311003.61001.9100
All Tests0.341001.61000.98100

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 SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embeddedEclipseLink
MySQL server
ObjectDB embedded
Basic Person Test1.31004.21002.7100
Element Collection Test0.691000.891000.79100
Inheritance Test1.11004.81002.9100
Indexing Test1.41004.91003.2100
Graph (Binary Tree) Test0.8597.10.731000.7998.5
Multithreading Test2.01004.01003.0100
All Tests1.299.63.31002.399.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.

Other Head to Head DBMS/JPA Comparisons