Compare with

Comparison of EclipseLink with H2 embedded 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 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB server
Basic Person Test25.135.28.974.117.054.7
Element Collection Test20.438.28.057.814.248.0
Inheritance Test28.732.78.772.818.752.7
Indexing Test37.649.914.090.125.870.0
Graph (Binary Tree) Test17.710014.789.216.294.6
Multithreading Test30.376.611.499.420.888.0
All Tests26.655.410.980.618.868.0

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

A large performance gap has been detected when using multithreading with large transaction size. Comparing the normalized speed of EclipseLink with H2 embedded database (11.4) to the normalized speed of ObjectDB database server (99.4) reveals that in that case, ObjectDB server is 8.7 times faster than EclipseLink with H2 embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB server
Basic Person Test30.415.729.145.429.730.5
Element Collection Test19.619.927.649.223.634.6
Inheritance Test33.813.239.849.436.831.3
Indexing Test22.214.041.359.531.836.8
Graph (Binary Tree) Test16.019.920.024.718.022.3
Multithreading Test33.719.729.060.231.440.0
All Tests25.917.131.148.128.532.6

The results above show that in general ObjectDB server is slightly more efficient than EclipseLink with H2 embedded in retrieving JPA entity objects from the database.

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

On the other hand, ObjectDB server is slower, for instance, when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of ObjectDB database server (13.2) to the normalized speed of EclipseLink with H2 embedded database (33.8) reveals that in that case, ObjectDB server is 2.6 times slower than EclipseLink with H2 embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB server
Basic Person Test4.438.81.425.92.932.4
Element Collection Test4.139.52.433.13.236.3
Inheritance Test3.434.82.034.02.734.4
Indexing Test13.014.522.853.317.933.9
Multithreading Test1.050.80.6752.10.8551.5
All Tests5.235.75.939.75.537.7

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB server
Basic Person Test16.618.37.640.912.129.6
Element Collection Test15.321.110.553.712.937.4
Inheritance Test15.719.99.851.912.735.9
Indexing Test12.117.99.952.111.035.0
Graph (Binary Tree) Test13.742.67.024.110.333.3
Multithreading Test20.968.64.268.712.668.6
All Tests15.731.48.248.612.040.0

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB server
Basic Person Test35.120.219.667.727.444.0
Element Collection Test19.322.98.557.613.940.2
Inheritance Test36.023.114.061.625.042.3
Indexing Test42.534.919.255.930.945.4
Graph (Binary Tree) Test12.219.314.427.913.323.6
Multithreading Test54.438.525.850.540.144.5
All Tests33.326.516.953.525.140.0

The results above show that in general ObjectDB server is more efficient than EclipseLink with H2 embedded in deleting JPA entity objects from the database.

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB serverEclipseLink
H2 embedded
ObjectDB server
Basic Person Test22.325.613.350.817.838.2
Element Collection Test15.728.311.450.313.639.3
Inheritance Test23.524.714.953.919.239.3
Indexing Test25.526.221.562.223.544.2
Graph (Binary Tree) Test14.945.414.041.514.543.5
Multithreading Test28.150.814.266.221.158.5
All Tests21.933.114.954.618.443.9

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

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

Other Head to Head DBMS/JPA Comparisons