Make initialization great again #826

New issue

Closed

opened 2023-11-23 13:43:03 +00:00 by fyrchik · 0 comments

fyrchik commented

2023-11-23 13:43:03 +00:00

Owner

After #703 with the increase in the amount of databases, initialization times went up.
During initialization we create empty databases with similar structure, so here is an idea:

Create a "template" empty database
Copy it everywhere we need it. The size of initial DB is not too high so it can be stored in memory.

Problems to consider:

Interrupted initialization can now lead to a half-written db being there, it could not open. Probably can be solved with atomic rename.

Another idea to test is delayed initialization/on-demand creation, but it seems to introduce more changes and concurrent interactions in code.

After #703 with the increase in the amount of databases, initialization times went up. During initialization we create empty databases with similar structure, so here is an idea: 1. Create a "template" empty database 2. Copy it everywhere we need it. The size of initial DB is not too high so it can be stored in memory. Problems to consider: 1. Interrupted initialization can now lead to a half-written db being there, it could not open. Probably can be solved with atomic `rename`. Another idea to test is delayed initialization/on-demand creation, but it seems to introduce more changes and concurrent interactions in code.