Compare with

Comparison of EclipseLink with SQLite embedded vs DataNucleus 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
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
Basic Person Test0.0742.80.902.30.492.6
Element Collection Test0.0610.710.650.350.360.53
Inheritance Test0.0832.70.822.00.452.3
Indexing Test0.114.51.64.00.874.3
Graph (Binary Tree) Test0.240.620.910.530.570.57
Multithreading Test0.104.92.13.41.14.1
All Tests0.112.71.22.10.642.4

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
 EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
Basic Person Testfailed0.56failed6.3failed3.4
Element Collection Test0.00070.36failed0.930.00070.64
Inheritance Testfailed0.45failed6.8failed3.6
Indexing Testfailed0.50failed7.1failed3.8
Graph (Binary Tree) Testfailed0.22failed6.6failed3.4
Multithreading Testfailed1.2failed10.0failed5.6
All Tests0.00070.55failed6.30.00073.4

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
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
Basic Person Test1.237.7failed3.61.220.7
Element Collection Test0.2925.9failed1.40.2913.6
Inheritance Test0.696.5failed1.80.694.2
Indexing Test0.00080.030failed4.90.00082.5
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests0.5517.5failed2.90.5510.2

EclipseLink with SQLite embedded has failed in 6 tests (see exceptions). DataNucleus with Derby server has failed in 2 tests (see exceptions).

Speed comparison of JPA database update operations (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
Basic Person Testfailed1.1failed0.85failed0.99
Element Collection Test0.00160.81failed0.620.00160.71
Inheritance Testfailed1.2failed1.3failed1.2
Indexing Testfailed1.2failed1.5failed1.3
Graph (Binary Tree) Testfailed0.29failed0.41failed0.35
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests0.00160.93failed0.920.00160.92

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions). DataNucleus with Derby server has failed in 2 tests (see exceptions).

Speed comparison of JPA database removal operations (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
Basic Person Testfailed1.3failed1.3failed1.3
Element Collection Test0.00060.61failed0.330.00060.47
Inheritance Testfailed1.0failed1.3failed1.2
Indexing Testfailed2.3failed1.9failed2.1
Graph (Binary Tree) Testfailed0.26failed0.46failed0.36
Multithreading Testfailedfailedfailedfailedfailedfailed
All Tests0.00061.1failed1.10.00061.1

EclipseLink with SQLite embedded has failed in 11 tests (see exceptions). DataNucleus with Derby server has failed in 2 tests (see exceptions).

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
EclipseLink
SQLite embedded
DataNucleus
Derby server
Basic Person Test0.668.70.902.90.745.8
Element Collection Test0.0705.70.650.720.173.2
Inheritance Test0.382.40.822.60.532.5
Indexing Test0.0581.71.63.90.582.8
Graph (Binary Tree) Test0.240.350.912.00.571.2
Multithreading Test0.103.02.16.71.14.9
All Tests0.223.81.22.80.523.3

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