Compare with

Comparison of EclipseLink with H2 server vs ObjectDB 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
 EclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB server
Basic Person Test5.635.22.574.14.054.7
Element Collection Test4.238.21.557.82.848.0
Inheritance Test6.632.72.172.84.452.7
Indexing Test9.749.94.190.16.970.0
Graph (Binary Tree) Test4.71003.589.24.194.6
Multithreading Test10.276.64.099.47.188.0
All Tests6.855.42.980.64.968.0

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

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

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB server
Basic Person Test5.515.78.245.46.830.5
Element Collection Test3.219.94.249.23.734.6
Inheritance Test4.713.210.149.47.431.3
Indexing Test4.414.09.459.56.936.8
Graph (Binary Tree) Test1.119.91.924.71.522.3
Multithreading Test12.219.715.960.214.040.0
All Tests5.217.18.348.16.732.6

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

A huge performance gap has been detected when using graphs of objects with small retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (1.1) to the normalized speed of ObjectDB database server (19.9) reveals that in that case, ObjectDB server is 18.1 times faster than EclipseLink with H2 server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB server
Basic Person Test3.838.81.125.92.532.4
Element Collection Test4.139.51.133.12.636.3
Inheritance Test3.234.81.334.02.334.4
Indexing Test3.014.58.053.35.533.9
Multithreading Test1.150.81.052.11.151.5
All Tests3.035.72.539.72.837.7

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

A huge performance gap has been detected when using multithreading with large retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (1.0) to the normalized speed of ObjectDB database server (52.1) reveals that in that case, ObjectDB server is 52.1 times faster than EclipseLink with H2 server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB server
Basic Person Test4.518.32.240.93.429.6
Element Collection Test3.821.12.453.73.137.4
Inheritance Test4.419.93.051.93.735.9
Indexing Test4.217.93.152.13.735.0
Graph (Binary Tree) Test1.442.60.7924.11.133.3
Multithreading Test7.868.62.568.75.168.6
All Tests4.331.42.348.63.340.0

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB server
Basic Person Test6.420.23.167.74.844.0
Element Collection Test3.022.91.357.62.240.2
Inheritance Test5.623.12.861.64.242.3
Indexing Test10.334.93.855.97.045.4
Graph (Binary Tree) Test1.519.31.327.91.423.6
Multithreading Test7.038.54.950.56.044.5
All Tests5.626.52.953.54.340.0

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

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB serverEclipseLink
H2 server
ObjectDB server
Basic Person Test5.225.63.450.84.338.2
Element Collection Test3.628.32.150.32.939.3
Inheritance Test4.924.73.953.94.439.3
Indexing Test6.326.25.762.26.044.2
Graph (Binary Tree) Test2.145.41.941.52.043.5
Multithreading Test7.750.85.766.26.758.5
All Tests5.133.13.854.64.543.9

The results above show that in general ObjectDB server is much more efficient than EclipseLink with H2 server in performing JPA database operations. Comparing the normalized speed of EclipseLink with H2 database server (4.5) to the normalized speed of ObjectDB database server (43.9) reveals that in these tests, ObjectDB server is 9.8 times faster than EclipseLink with H2 server.

A huge performance gap has been detected when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of EclipseLink with H2 database server (2.1) to the normalized speed of ObjectDB database server (50.3) reveals that in that case, ObjectDB server is 24.0 times faster than EclipseLink with H2 server.

Other Head to Head DBMS/JPA Comparisons