Compare with

Comparison of EclipseLink with Derby server 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 server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
Basic Person Test3.80.0743.10.903.40.49
Element Collection Test2.20.0611.50.651.80.36
Inheritance Test3.90.0832.90.823.40.45
Indexing Test5.20.114.31.64.70.87
Graph (Binary Tree) Test1.90.241.70.911.80.57
Multithreading Test6.10.103.92.15.01.1
All Tests3.80.112.91.23.40.64

The results above show that in general EclipseLink with Derby server 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 database server (3.4) reveals that in these tests, EclipseLink with Derby server is 5.3 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 database server (6.1) reveals that in that case, EclipseLink with Derby server is 61.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 server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
Basic Person Test6.4failed11.3failed8.8failed
Element Collection Test1.80.00072.4failed2.10.0007
Inheritance Test3.7failed12.9failed8.3failed
Indexing Test3.6failed12.8failed8.2failed
Graph (Binary Tree) Test0.61failed0.73failed0.67failed
Multithreading Test8.5failed19.8failed14.1failed
All Tests4.10.000710.0failed7.00.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 server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
Basic Person Test45.81.25.3failed25.61.2
Element Collection Test35.20.290.99failed18.10.29
Inheritance Test23.10.695.9failed14.50.69
Indexing Test2.50.000812.2failed7.40.0008
Multithreading Test34.3failed7.7failed21.0failed
All Tests28.20.556.4failed17.30.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 server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
Basic Person Test3.9failed4.4failed4.1failed
Element Collection Test1.70.00161.6failed1.60.0016
Inheritance Test4.6failed6.1failed5.3failed
Indexing Test4.5failed7.6failed6.1failed
Graph (Binary Tree) Test0.70failed0.42failed0.56failed
Multithreading Test7.3failed4.8failed6.0failed
All Tests3.80.00164.2failed4.00.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 server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
Basic Person Test2.8failed3.9failed3.3failed
Element Collection Test1.20.00060.55failed0.870.0006
Inheritance Test3.3failed3.7failed3.5failed
Indexing Test4.9failed3.5failed4.2failed
Graph (Binary Tree) Test0.51failed0.50failed0.51failed
Multithreading Test4.8failed5.7failed5.3failed
All Tests2.90.00063.0failed3.00.0006

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
Basic Person Test12.50.665.60.909.10.74
Element Collection Test8.40.0701.40.654.90.17
Inheritance Test7.70.386.30.827.00.53
Indexing Test4.10.0588.11.66.10.58
Graph (Binary Tree) Test0.930.240.830.910.880.57
Multithreading Test12.20.108.42.110.31.1
All Tests7.90.225.21.26.60.52

The results above show that in general EclipseLink with Derby server 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 database server (6.6) reveals that in these tests, EclipseLink with Derby server is 12.7 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 database server (12.2) reveals that in that case, EclipseLink with Derby server is 122 times faster than EclipseLink with SQLite embedded.

Other Head to Head DBMS/JPA Comparisons