Compare with

Comparison of DataNucleus 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
 DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test4.60.0742.80.903.70.49
Element Collection Test2.40.0611.60.652.00.36
Inheritance Test4.60.0832.70.823.70.45
Indexing Test7.60.114.81.66.20.87
Graph (Binary Tree) Test1.60.241.40.911.50.57
Multithreading Test8.60.103.32.15.91.1
All Tests4.90.112.81.23.80.64

The results above show that in general DataNucleus 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 DataNucleus with Derby embedded database (3.8) reveals that in these tests, DataNucleus with Derby embedded is 5.9 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 DataNucleus with Derby embedded database (8.6) reveals that in that case, DataNucleus with Derby embedded is 86.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
 DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test6.8failed14.9failed10.9failed
Element Collection Test5.40.00077.6failed6.50.0007
Inheritance Test8.8failed14.8failed11.8failed
Indexing Test9.2failed14.1failed11.6failed
Graph (Binary Tree) Test9.9failed15.8failed12.9failed
Multithreading Test11.9failed11.5failed11.7failed
All Tests8.70.000713.1failed10.90.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
 DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test39.11.27.5failed23.31.2
Element Collection Test46.00.296.7failed26.30.29
Inheritance Test7.70.693.8failed5.70.69
Indexing Test0.0530.00088.0failed4.00.0008
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests23.20.556.5failed14.80.55

DataNucleus with Derby embedded has failed in 2 tests (see exceptions). 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
 DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test4.0failed3.8failed3.9failed
Element Collection Test3.70.00164.5failed4.10.0016
Inheritance Test4.4failed4.8failed4.6failed
Indexing Test5.2failed4.2failed4.7failed
Graph (Binary Tree) Test2.7failed1.5failed2.1failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests4.00.00163.7failed3.90.0016

DataNucleus with Derby embedded has failed in 2 tests (see exceptions). 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
 DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test3.5failed1.3failed2.4failed
Element Collection Test1.90.00061.6failed1.70.0006
Inheritance Test2.4failed1.3failed1.9failed
Indexing Test6.6failed1.9failed4.3failed
Graph (Binary Tree) Test0.81failed0.93failed0.87failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests3.00.00061.4failed2.20.0006

DataNucleus with Derby embedded has failed in 2 tests (see exceptions). 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
 DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test53.379.453.379.453.379.4
Element Collection Test42.674.542.674.542.674.5
Inheritance Test48.175.048.175.048.175.0
Indexing Test62.392.963.394.562.893.7
Graph (Binary Tree) Test13.660.610.248.411.954.5
Multithreading Test52.01008.010030.0100
All Tests45.380.437.678.641.579.5

The results above show that in general EclipseLink with SQLite embedded is more efficient than DataNucleus with Derby embedded in using disk space.

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
DataNucleus
Derby embedded
EclipseLink
SQLite embedded
Basic Person Test11.60.666.10.908.80.74
Element Collection Test11.90.0704.40.658.10.17
Inheritance Test5.60.385.50.825.50.53
Indexing Test5.70.0586.61.66.20.58
Graph (Binary Tree) Test3.70.244.90.914.30.57
Multithreading Test10.30.107.42.18.81.1
All Tests8.00.225.71.26.90.52

The results above show that in general DataNucleus 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 DataNucleus with Derby embedded database (6.9) reveals that in these tests, DataNucleus with Derby embedded is 13.3 times faster than EclipseLink with SQLite embedded.

A huge performance gap has been detected when using JPA element collections with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.070) to the normalized speed of DataNucleus with Derby embedded database (11.9) reveals that in that case, DataNucleus with Derby embedded is 170 times faster than EclipseLink with SQLite embedded.

Other Head to Head DBMS/JPA Comparisons