Compare with

Comparison of EclipseLink with Derby embedded vs EclipseLink with SQLite embedded

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
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test5.50.0743.70.904.60.49
Element Collection Test3.00.0611.70.652.40.36
Inheritance Test5.30.0833.50.824.40.45
Indexing Test6.90.114.61.65.80.87
Graph (Binary Tree) Test2.00.241.90.911.90.57
Multithreading Test9.30.104.12.16.71.1
All Tests5.30.113.21.24.30.64

The results above show that in general EclipseLink with Derby embedded is much more efficient than EclipseLink with SQLite embedded in persisting JPA entity objects to the database. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.64) to the normalized speed of EclipseLink with Derby embedded database (4.3) reveals that in these tests, EclipseLink with Derby embedded is 6.7 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using multithreading with small transaction size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.10) to the normalized speed of EclipseLink with Derby embedded database (9.3) reveals that in that case, EclipseLink with Derby embedded is 93.0 times faster than EclipseLink with SQLite embedded.

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test16.4failed58.7failed37.5failed
Element Collection Test7.50.000713.3failed10.40.0007
Inheritance Test17.1failed58.9failed38.0failed
Indexing Test14.2failed67.4failed40.8failed
Graph (Binary Tree) Test2.8failed5.7failed4.2failed
Multithreading Test28.0failed48.7failed38.4failed
All Tests14.30.000742.1failed28.20.0007

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test53.41.213.8failed33.61.2
Element Collection Test37.90.294.4failed21.20.29
Inheritance Test37.40.6915.0failed26.20.69
Indexing Test7.60.000849.3failed28.40.0008
Multithreading Test41.2failed6.1failed23.6failed
All Tests35.50.5517.7failed26.60.55

EclipseLink with SQLite embedded has failed in 6 tests (see exceptions).

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test6.4failed6.7failed6.5failed
Element Collection Test5.40.00166.2failed5.80.0016
Inheritance Test6.5failed9.2failed7.8failed
Indexing Test7.3failed11.1failed9.2failed
Graph (Binary Tree) Test2.8failed1.7failed2.2failed
Multithreading Test21.3failed5.0failed13.1failed
All Tests8.30.00166.6failed7.50.0016

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

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

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test4.6failed4.7failed4.6failed
Element Collection Test2.50.00061.4failed1.90.0006
Inheritance Test3.9failed4.5failed4.2failed
Indexing Test6.2failed3.8failed5.0failed
Graph (Binary Tree) Test1.1failed1.0failed1.1failed
Multithreading Test6.2failed5.8failed6.0failed
All Tests4.10.00063.5failed3.80.0006

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions).

Comparison of database storage efficiency (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test51.179.451.079.451.179.4
Element Collection Test38.574.539.474.538.974.5
Inheritance Test48.075.047.975.048.075.0
Indexing Test51.692.952.394.552.093.7
Graph (Binary Tree) Test13.460.611.748.412.654.5
Multithreading Test52.61008.410030.5100
All Tests42.580.435.178.638.879.5

The results above show that in general EclipseLink with SQLite embedded is more efficient than EclipseLink with Derby embedded in using disk space. Comparing the normalized score of EclipseLink with Derby embedded database (38.8) to the normalized score of EclipseLink with SQLite embedded database (79.5) reveals that in these tests, EclipseLink with SQLite embedded is 2.0 times more efficient than EclipseLink with Derby embedded.

A huge gap has been detected when using multithreading with large transaction size. Comparing the normalized score of EclipseLink with Derby embedded database (8.4) to the normalized score of EclipseLink with SQLite embedded database (100) reveals that in that case, EclipseLink with SQLite embedded is 11.9 times more efficient than EclipseLink with Derby embedded.

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test17.30.6617.50.9017.40.74
Element Collection Test11.30.0705.40.658.30.17
Inheritance Test14.00.3818.20.8216.10.53
Indexing Test8.40.05827.21.617.80.58
Graph (Binary Tree) Test2.20.242.60.912.40.57
Multithreading Test21.20.1013.92.117.61.1
All Tests12.70.2214.51.213.60.52

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

A huge performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.10) to the normalized speed of EclipseLink with Derby embedded database (21.2) reveals that in that case, EclipseLink with Derby embedded is 212 times faster than EclipseLink with SQLite embedded.

Other Head to Head DBMS/JPA Comparisons