Split database into "active" and "archived"?
Closed this issue · 2 comments
neonrust commented
As the database grows, it makes sense to move the non-changing entries (i.e. the archived) into a separate database file.
This will make it more awkward to perform the "all" listings. Not by a lot though.
neonrust commented
However, slow reading/writing the database probably doesn't become an issue until the database has at least a 1000 series in it (depends on how big they are, of course).
On my machine (i5-8400), at ~160 entries (4.5 MiB), it takes ~25ms (read) and ~120ms (write). (and my CPU is arguably on the low-end of things)