Compare with

Comparison of EclipseLink with Derby embedded vs EclipseLink with Derby 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
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
Basic Person Test5.53.83.73.14.63.4
Element Collection Test3.02.21.71.52.41.8
Inheritance Test5.33.93.52.94.43.4
Indexing Test6.95.24.64.35.84.7
Graph (Binary Tree) Test2.01.91.91.71.91.8
Multithreading Test9.36.14.13.96.75.0
All Tests5.33.83.22.94.33.4

The results above show that in general EclipseLink with Derby embedded is slightly more efficient than EclipseLink with Derby server in persisting JPA entity objects to the database.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
Basic Person Test16.46.458.711.337.58.8
Element Collection Test7.51.813.32.410.42.1
Inheritance Test17.13.758.912.938.08.3
Indexing Test14.23.667.412.840.88.2
Graph (Binary Tree) Test2.80.615.70.734.20.67
Multithreading Test28.08.548.719.838.414.1
All Tests14.34.142.110.028.27.0

The results above show that in general EclipseLink with Derby embedded is much more efficient than EclipseLink with Derby server in retrieving JPA entity objects from the database. Comparing the normalized speed of EclipseLink with Derby database server (7.0) to the normalized speed of EclipseLink with Derby embedded database (28.2) reveals that in these tests, EclipseLink with Derby embedded is 4.0 times faster than EclipseLink with Derby server.

A large performance gap has been detected when using graphs of objects with large retrieval size. Comparing the normalized speed of EclipseLink with Derby database server (0.73) to the normalized speed of EclipseLink with Derby embedded database (5.7) reveals that in that case, EclipseLink with Derby embedded is 7.8 times faster than EclipseLink with Derby server.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
Basic Person Test53.445.813.85.333.625.6
Element Collection Test37.935.24.40.9921.218.1
Inheritance Test37.423.115.05.926.214.5
Indexing Test7.62.549.312.228.47.4
Multithreading Test41.234.36.17.723.621.0
All Tests35.528.217.76.426.617.3

The results above show that in general EclipseLink with Derby embedded is more efficient than EclipseLink with Derby server in executing the tested JPA queries.

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

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
Basic Person Test6.43.96.74.46.54.1
Element Collection Test5.41.76.21.65.81.6
Inheritance Test6.54.69.26.17.85.3
Indexing Test7.34.511.17.69.26.1
Graph (Binary Tree) Test2.80.701.70.422.20.56
Multithreading Test21.37.35.04.813.16.0
All Tests8.33.86.64.27.54.0

The results above show that in general EclipseLink with Derby embedded is more efficient than EclipseLink with Derby server in updating JPA entity objects in the database.

A large performance gap has been detected when using graphs of objects with large transaction size. Comparing the normalized speed of EclipseLink with Derby database server (0.42) to the normalized speed of EclipseLink with Derby embedded database (1.7) reveals that in that case, EclipseLink with Derby embedded is 4.0 times faster than EclipseLink with Derby server.

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
Basic Person Test4.62.84.73.94.63.3
Element Collection Test2.51.21.40.551.90.87
Inheritance Test3.93.34.53.74.23.5
Indexing Test6.24.93.83.55.04.2
Graph (Binary Tree) Test1.10.511.00.501.10.51
Multithreading Test6.24.85.85.76.05.3
All Tests4.12.93.53.03.83.0

The results above show that in general EclipseLink with Derby embedded is slightly more efficient than EclipseLink with Derby server 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 Derby database server (0.55) to the normalized speed of EclipseLink with Derby embedded database (1.4) reveals that in that case, EclipseLink with Derby embedded is 2.5 times faster than EclipseLink with Derby server.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
EclipseLink
Derby embedded
EclipseLink
Derby server
Basic Person Test17.312.517.55.617.49.1
Element Collection Test11.38.45.41.48.34.9
Inheritance Test14.07.718.26.316.17.0
Indexing Test8.44.127.28.117.86.1
Graph (Binary Tree) Test2.20.932.60.832.40.88
Multithreading Test21.212.213.98.417.610.3
All Tests12.77.914.55.213.66.6

The results above show that in general EclipseLink with Derby embedded is more efficient than EclipseLink with Derby server in performing JPA database operations. Comparing the normalized speed of EclipseLink with Derby database server (6.6) to the normalized speed of EclipseLink with Derby embedded database (13.6) reveals that in these tests, EclipseLink with Derby embedded is 2.1 times faster than EclipseLink with Derby server.

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

Other Head to Head DBMS/JPA Comparisons