Compare with

Comparison of DataNucleus 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
 DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
Basic Person Test2.80.0742.30.902.60.49
Element Collection Test0.710.0610.350.650.530.36
Inheritance Test2.70.0832.00.822.30.45
Indexing Test4.50.114.01.64.30.87
Graph (Binary Tree) Test0.620.240.530.910.570.57
Multithreading Test4.90.103.42.14.11.1
All Tests2.70.112.11.22.40.64

The results above show that in general DataNucleus 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 DataNucleus with Derby database server (2.4) reveals that in these tests, DataNucleus with Derby server is 3.8 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 database server (4.9) reveals that in that case, DataNucleus with Derby server is 49.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 server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
Basic Person Test0.56failed6.3failed3.4failed
Element Collection Test0.360.00070.93failed0.640.0007
Inheritance Test0.45failed6.8failed3.6failed
Indexing Test0.50failed7.1failed3.8failed
Graph (Binary Tree) Test0.22failed6.6failed3.4failed
Multithreading Test1.2failed10.0failed5.6failed
All Tests0.550.00076.3failed3.40.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 server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
Basic Person Test37.71.23.6failed20.71.2
Element Collection Test25.90.291.4failed13.60.29
Inheritance Test6.50.691.8failed4.20.69
Indexing Test0.0300.00084.9failed2.50.0008
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests17.50.552.9failed10.20.55

DataNucleus with Derby server 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 server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
Basic Person Test1.1failed0.85failed0.99failed
Element Collection Test0.810.00160.62failed0.710.0016
Inheritance Test1.2failed1.3failed1.2failed
Indexing Test1.2failed1.5failed1.3failed
Graph (Binary Tree) Test0.29failed0.41failed0.35failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests0.930.00160.92failed0.920.0016

DataNucleus with Derby server 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 server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
Basic Person Test1.3failed1.3failed1.3failed
Element Collection Test0.610.00060.33failed0.470.0006
Inheritance Test1.0failed1.3failed1.2failed
Indexing Test2.3failed1.9failed2.1failed
Graph (Binary Tree) Test0.26failed0.46failed0.36failed
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests1.10.00061.1failed1.10.0006

DataNucleus with Derby server has failed in 2 tests (see exceptions). 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
 DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
Basic Person Test8.70.662.90.905.80.74
Element Collection Test5.70.0700.720.653.20.17
Inheritance Test2.40.382.60.822.50.53
Indexing Test1.70.0583.91.62.80.58
Graph (Binary Tree) Test0.350.242.00.911.20.57
Multithreading Test3.00.106.72.14.91.1
All Tests3.80.222.81.23.30.52

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

Other Head to Head DBMS/JPA Comparisons