Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to a better db for cached results #155

Open
alexheretic opened this issue Aug 31, 2023 · 1 comment
Open

Switch to a better db for cached results #155

alexheretic opened this issue Aug 31, 2023 · 1 comment

Comments

@alexheretic
Copy link
Owner

An embedded db is used to cache sample-encode results. The current db sled isn't an ideal for here as it doesn't support concurrent access from multiple processes. There have also been a couple of reported db corruption cases, presumably from killing the process.

So time to try a different one. I'd prefer a nosql kv store but maybe sqlite will end up best?

@mr44er
Copy link

mr44er commented Sep 24, 2023

I don't know the differences between all of these DBs with this use case, but I'm up to testing and reporting how it behaves! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants