Compare with

Comparison of EclipseLink with HSQLDB 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
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB server
Basic Person Test27.135.217.274.122.254.7
Element Collection Test17.238.28.257.812.748.0
Inheritance Test26.732.711.972.819.352.7
Indexing Test30.649.918.690.124.670.0
Graph (Binary Tree) Test20.010015.989.218.094.6
Multithreading Test32.576.611.499.422.088.0
All Tests25.755.413.980.619.868.0

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

A large performance gap has been detected when using multithreading with large transaction size. Comparing the normalized speed of EclipseLink with HSQLDB 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 HSQLDB embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB server
Basic Person Test24.415.736.045.430.230.5
Element Collection Test14.919.919.149.217.034.6
Inheritance Test22.813.240.049.431.431.3
Indexing Test20.714.038.759.529.736.8
Graph (Binary Tree) Test8.719.914.224.711.422.3
Multithreading Test24.219.728.060.226.140.0
All Tests19.317.129.348.124.332.6

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

A large performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of EclipseLink with HSQLDB embedded database (19.1) to the normalized speed of ObjectDB database server (49.2) reveals that in that case, ObjectDB server is 2.6 times faster than EclipseLink with HSQLDB embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB server
Basic Person Test2.938.80.8825.91.932.4
Element Collection Test3.239.51.433.12.336.3
Inheritance Test2.634.81.134.01.934.4
Indexing Test21.514.533.353.327.433.9
Multithreading Test1.150.80.5252.10.8251.5
All Tests6.335.77.439.76.937.7

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB server
Basic Person Test17.918.37.040.912.529.6
Element Collection Test14.621.18.353.711.437.4
Inheritance Test16.219.99.751.913.035.9
Indexing Test12.017.96.852.19.435.0
Graph (Binary Tree) Test4.742.63.424.14.033.3
Multithreading Test24.468.64.468.714.468.6
All Tests15.031.46.648.610.840.0

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

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB server
Basic Person Test32.320.220.367.726.344.0
Element Collection Test14.322.96.057.610.240.2
Inheritance Test29.223.123.961.626.642.3
Indexing Test55.334.927.155.941.245.4
Graph (Binary Tree) Test6.819.314.127.910.423.6
Multithreading Test52.938.528.450.540.644.5
All Tests31.826.520.053.525.940.0

The results above show that in general ObjectDB server is more efficient than EclipseLink with HSQLDB 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 HSQLDB embedded database (6.0) to the normalized speed of ObjectDB database server (57.6) reveals that in that case, ObjectDB server is 9.6 times faster than EclipseLink with HSQLDB embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB serverEclipseLink
HSQLDB embedded
ObjectDB server
Basic Person Test20.925.616.350.818.638.2
Element Collection Test12.828.38.650.310.739.3
Inheritance Test19.524.717.353.918.439.3
Indexing Test28.026.224.962.226.544.2
Graph (Binary Tree) Test10.045.411.941.511.043.5
Multithreading Test27.050.814.666.220.858.5
All Tests20.133.115.754.617.943.9

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

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

Other Head to Head DBMS/JPA Comparisons