Syncing from scratch with SQLiteStorage on disk (not in memory) is very slow. This is presumably caused (at least in part) by the need to synchronise changes to disk for each committed transaction.
Instead of doing one transaction per block (which is the default mode of operation for Game), we could batch many blocks together while catching up. This would allow faster operations in the SQLite database (and in fact also for non-SQLite storages that may have a similar issue), at the cost of losing more data when a failure happens. (But that would just mean that more blocks have to be resynchronised after a restart.)
Syncing from scratch with
SQLiteStorageon disk (not in memory) is very slow. This is presumably caused (at least in part) by the need to synchronise changes to disk for each committed transaction.Instead of doing one transaction per block (which is the default mode of operation for
Game), we could batch many blocks together while catching up. This would allow faster operations in the SQLite database (and in fact also for non-SQLite storages that may have a similar issue), at the cost of losing more data when a failure happens. (But that would just mean that more blocks have to be resynchronised after a restart.)