Compare with

Comparison of EclipseLink with SQLite 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
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
Basic Person Test0.0743.80.903.10.493.4
Element Collection Test0.0612.20.651.50.361.8
Inheritance Test0.0833.90.822.90.453.4
Indexing Test0.115.21.64.30.874.7
Graph (Binary Tree) Test0.241.90.911.70.571.8
Multithreading Test0.106.12.13.91.15.0
All Tests0.113.81.22.90.643.4

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
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
Basic Person Testfailed6.4failed11.3failed8.8
Element Collection Test0.00071.8failed2.40.00072.1
Inheritance Testfailed3.7failed12.9failed8.3
Indexing Testfailed3.6failed12.8failed8.2
Graph (Binary Tree) Testfailed0.61failed0.73failed0.67
Multithreading Testfailed8.5failed19.8failed14.1
All Tests0.00074.1failed10.00.00077.0

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
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
Basic Person Test1.245.8failed5.31.225.6
Element Collection Test0.2935.2failed0.990.2918.1
Inheritance Test0.6923.1failed5.90.6914.5
Indexing Test0.00082.5failed12.20.00087.4
Multithreading Testfailed34.3failed7.7failed21.0
All Tests0.5528.2failed6.40.5517.3

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
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
Basic Person Testfailed3.9failed4.4failed4.1
Element Collection Test0.00161.7failed1.60.00161.6
Inheritance Testfailed4.6failed6.1failed5.3
Indexing Testfailed4.5failed7.6failed6.1
Graph (Binary Tree) Testfailed0.70failed0.42failed0.56
Multithreading Testfailed7.3failed4.8failed6.0
All Tests0.00163.8failed4.20.00164.0

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
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
Basic Person Testfailed2.8failed3.9failed3.3
Element Collection Test0.00061.2failed0.550.00060.87
Inheritance Testfailed3.3failed3.7failed3.5
Indexing Testfailed4.9failed3.5failed4.2
Graph (Binary Tree) Testfailed0.51failed0.50failed0.51
Multithreading Testfailed4.8failed5.7failed5.3
All Tests0.00062.9failed3.00.00063.0

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
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
EclipseLink
SQLite embedded
EclipseLink
Derby server
Basic Person Test0.6612.50.905.60.749.1
Element Collection Test0.0708.40.651.40.174.9
Inheritance Test0.387.70.826.30.537.0
Indexing Test0.0584.11.68.10.586.1
Graph (Binary Tree) Test0.240.930.910.830.570.88
Multithreading Test0.1012.22.18.41.110.3
All Tests0.227.91.25.20.526.6

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