Replace VC cache backend with embedded database

[romac]

[romac]

For large projects, where the cache can easily grow over 2GB, the performance of the current caching backend really suffers and has quite an impact on overall verification time (5-10s of cache loading for each run).

I think it would be valuable to re-prioritize this issue. I don’t know if Sway is still (or even ever was) the best solution, so some investigation into embedded databases is probably still needed.

[simerplaha]

Hi, just checking to see if you need help validating SwayDB.

These links might help - benchmarks, caching & blogs. Caching is very configurable depending on the use-case. It can be enabled for your entire 2GB file, parts of that file or you can have multiple smaller files with memory-mapped enabled or disabled or just for caching individual key-values on access.

As far as being the best solution goes, that's always been the goal but I should point out that it at version zero (0.13.4) - see project status.

[romac]

We won't go with SwayDB because of its license, so we need to find another embedded database with support for persistent sets.