Compare with

Comparison of EclipseLink with SQLite embedded vs EclipseLink with Derby 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
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
Basic Person Test0.0745.50.903.70.494.6
Element Collection Test0.0613.00.651.70.362.4
Inheritance Test0.0835.30.823.50.454.4
Indexing Test0.116.91.64.60.875.8
Graph (Binary Tree) Test0.242.00.911.90.571.9
Multithreading Test0.109.32.14.11.16.7
All Tests0.115.31.23.20.644.3

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
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
Basic Person Testfailed16.4failed58.7failed37.5
Element Collection Test0.00077.5failed13.30.000710.4
Inheritance Testfailed17.1failed58.9failed38.0
Indexing Testfailed14.2failed67.4failed40.8
Graph (Binary Tree) Testfailed2.8failed5.7failed4.2
Multithreading Testfailed28.0failed48.7failed38.4
All Tests0.000714.3failed42.10.000728.2

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 embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
Basic Person Test1.253.4failed13.81.233.6
Element Collection Test0.2937.9failed4.40.2921.2
Inheritance Test0.6937.4failed15.00.6926.2
Indexing Test0.00087.6failed49.30.000828.4
Multithreading Testfailed41.2failed6.1failed23.6
All Tests0.5535.5failed17.70.5526.6

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 embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
Basic Person Testfailed6.4failed6.7failed6.5
Element Collection Test0.00165.4failed6.20.00165.8
Inheritance Testfailed6.5failed9.2failed7.8
Indexing Testfailed7.3failed11.1failed9.2
Graph (Binary Tree) Testfailed2.8failed1.7failed2.2
Multithreading Testfailed21.3failed5.0failed13.1
All Tests0.00168.3failed6.60.00167.5

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 embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
Basic Person Testfailed4.6failed4.7failed4.6
Element Collection Test0.00062.5failed1.40.00061.9
Inheritance Testfailed3.9failed4.5failed4.2
Indexing Testfailed6.2failed3.8failed5.0
Graph (Binary Tree) Testfailed1.1failed1.0failed1.1
Multithreading Testfailed6.2failed5.8failed6.0
All Tests0.00064.1failed3.50.00063.8

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
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
Basic Person Test79.451.179.451.079.451.1
Element Collection Test74.538.574.539.474.538.9
Inheritance Test75.048.075.047.975.048.0
Indexing Test92.951.694.552.393.752.0
Graph (Binary Tree) Test60.613.448.411.754.512.6
Multithreading Test10052.61008.410030.5
All Tests80.442.578.635.179.538.8

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
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
EclipseLink
SQLite embedded
EclipseLink
Derby embedded
Basic Person Test0.6617.30.9017.50.7417.4
Element Collection Test0.07011.30.655.40.178.3
Inheritance Test0.3814.00.8218.20.5316.1
Indexing Test0.0588.41.627.20.5817.8
Graph (Binary Tree) Test0.242.20.912.60.572.4
Multithreading Test0.1021.22.113.91.117.6
All Tests0.2212.71.214.50.5213.6

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