Compare with

Comparison of EclipseLink with H2 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
 EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
Basic Person Test25.10.0748.90.9017.00.49
Element Collection Test20.40.0618.00.6514.20.36
Inheritance Test28.70.0838.70.8218.70.45
Indexing Test37.60.1114.01.625.80.87
Graph (Binary Tree) Test17.70.2414.70.9116.20.57
Multithreading Test30.30.1011.42.120.81.1
All Tests26.60.1110.91.218.80.64

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

A huge performance gap has been detected when using class inheritance in the object model with small transaction size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.083) to the normalized speed of EclipseLink with H2 embedded database (28.7) reveals that in that case, EclipseLink with H2 embedded is 346 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
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
Basic Person Test30.4failed29.1failed29.7failed
Element Collection Test19.60.000727.6failed23.60.0007
Inheritance Test33.8failed39.8failed36.8failed
Indexing Test22.2failed41.3failed31.8failed
Graph (Binary Tree) Test16.0failed20.0failed18.0failed
Multithreading Test33.7failed29.0failed31.4failed
All Tests25.90.000731.1failed28.50.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
 EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
Basic Person Test4.41.21.4failed2.91.2
Element Collection Test4.10.292.4failed3.20.29
Inheritance Test3.40.692.0failed2.70.69
Indexing Test13.00.000822.8failed17.90.0008
Multithreading Test1.0failed0.67failed0.85failed
All Tests5.20.555.9failed5.50.55

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
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
Basic Person Test16.6failed7.6failed12.1failed
Element Collection Test15.30.001610.5failed12.90.0016
Inheritance Test15.7failed9.8failed12.7failed
Indexing Test12.1failed9.9failed11.0failed
Graph (Binary Tree) Test13.7failed7.0failed10.3failed
Multithreading Test20.9failed4.2failed12.6failed
All Tests15.70.00168.2failed12.00.0016

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
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
Basic Person Test35.1failed19.6failed27.4failed
Element Collection Test19.30.00068.5failed13.90.0006
Inheritance Test36.0failed14.0failed25.0failed
Indexing Test42.5failed19.2failed30.9failed
Graph (Binary Tree) Test12.2failed14.4failed13.3failed
Multithreading Test54.4failed25.8failed40.1failed
All Tests33.30.000616.9failed25.10.0006

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
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
Basic Person Test36.279.439.279.437.779.4
Element Collection Test33.374.534.974.534.174.5
Inheritance Test35.475.036.275.035.875.0
Indexing Test39.892.943.794.541.793.7
Graph (Binary Tree) Test41.060.628.448.434.754.5
Multithreading Test48.710012.410030.6100
All Tests39.180.432.578.635.879.5

The results above show that in general EclipseLink with SQLite embedded is more efficient than EclipseLink with H2 embedded in using disk space. Comparing the normalized score of EclipseLink with H2 embedded database (35.8) to the normalized score of EclipseLink with SQLite embedded database (79.5) reveals that in these tests, EclipseLink with SQLite embedded is 2.2 times more efficient than EclipseLink with H2 embedded.

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

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

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
EclipseLink
H2 embedded
EclipseLink
SQLite embedded
Basic Person Test22.30.6613.30.9017.80.74
Element Collection Test15.70.07011.40.6513.60.17
Inheritance Test23.50.3814.90.8219.20.53
Indexing Test25.50.05821.51.623.50.58
Graph (Binary Tree) Test14.90.2414.00.9114.50.57
Multithreading Test28.10.1014.22.121.11.1
All Tests21.90.2214.91.218.40.52

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

A huge performance gap has been detected when using database indexes with small transaction/retrieval size. Comparing the normalized speed of EclipseLink with SQLite embedded database (0.058) to the normalized speed of EclipseLink with H2 embedded database (25.5) reveals that in that case, EclipseLink with H2 embedded is 440 times faster than EclipseLink with SQLite embedded.

Other Head to Head DBMS/JPA Comparisons