Compare with

Comparison of ObjectDB server vs EclipseLink with MySQL 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 EntitiesMany EntitiesAverage Score
 ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
Basic Person Test35.23.674.11.554.72.6
Element Collection Test38.21.557.80.6948.01.1
Inheritance Test32.73.572.81.452.72.4
Indexing Test49.95.390.12.570.03.9
Graph (Binary Tree) Test1001.789.21.394.61.5
Multithreading Test76.67.299.42.488.04.8
All Tests55.43.880.61.668.02.7

The results above show that in general ObjectDB server 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 database server (68.0) reveals that in these tests, ObjectDB server is 25.2 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 database server (57.8) reveals that in that case, ObjectDB server is 83.8 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
 ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
Basic Person Test15.70.4345.415.530.58.0
Element Collection Test19.90.1649.21.434.60.78
Inheritance Test13.20.3949.417.631.39.0
Indexing Test14.00.4359.516.636.88.5
Graph (Binary Tree) Test19.90.5324.70.7622.30.65
Multithreading Test19.70.1960.211.040.05.6
All Tests17.10.3548.110.532.65.4

The results above show that in general ObjectDB server 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 database server (32.6) reveals that in these tests, ObjectDB server is 6.0 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 database server (19.9) reveals that in that case, ObjectDB server is 124 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
 ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
Basic Person Test38.81.525.90.4432.40.95
Element Collection Test39.51.433.10.4336.30.92
Inheritance Test34.81.134.00.6134.40.86
Indexing Test14.50.2653.30.5233.90.39
Multithreading Test50.81.952.10.7251.51.3
All Tests35.71.239.70.5437.70.88

The results above show that in general ObjectDB server 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 database server (37.7) reveals that in these tests, ObjectDB server is 42.8 times faster than EclipseLink with MySQL server.

A huge performance gap has been detected when using database indexes with large retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.52) to the normalized speed of ObjectDB database server (53.3) reveals that in that case, ObjectDB server is 102 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
 ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
Basic Person Test18.30.3940.91.829.61.1
Element Collection Test21.10.2353.71.437.40.83
Inheritance Test19.90.4251.92.635.91.5
Indexing Test17.90.4652.13.135.01.8
Graph (Binary Tree) Test42.60.6724.10.4133.30.54
Multithreading Test68.60.4868.72.668.61.5
All Tests31.40.4448.62.040.01.2

The results above show that in general ObjectDB server 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 database server (40.0) reveals that in these tests, ObjectDB server is 33.3 times faster than EclipseLink with MySQL server.

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with MySQL database server (0.48) to the normalized speed of ObjectDB database server (68.6) reveals that in that case, ObjectDB server is 143 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
 ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
Basic Person Test20.20.3567.71.744.01.0
Element Collection Test22.90.1157.60.5140.20.31
Inheritance Test23.10.2961.61.642.30.94
Indexing Test34.90.4655.91.945.41.2
Graph (Binary Tree) Test19.30.5427.90.4923.60.51
Multithreading Test38.50.3150.53.644.51.9
All Tests26.50.3453.51.640.00.98

The results above show that in general ObjectDB server 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 database server (40.0) reveals that in these tests, ObjectDB server is 40.8 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 database server (22.9) reveals that in that case, ObjectDB server is 208 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
 ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
ObjectDB serverEclipseLink
MySQL server
Basic Person Test25.61.350.84.238.22.7
Element Collection Test28.30.6950.30.8939.30.79
Inheritance Test24.71.153.94.839.32.9
Indexing Test26.21.462.24.944.23.2
Graph (Binary Tree) Test45.40.8541.50.7343.50.79
Multithreading Test50.82.066.24.058.53.0
All Tests33.11.254.63.343.92.3

The results above show that in general ObjectDB server 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 database server (43.9) reveals that in these tests, ObjectDB server is 19.1 times faster than EclipseLink with MySQL server.

A huge performance gap has been detected when using graphs of objects with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with MySQL database server (0.73) to the normalized speed of ObjectDB database server (41.5) reveals that in that case, ObjectDB server is 56.8 times faster than EclipseLink with MySQL server.

Other Head to Head DBMS/JPA Comparisons