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

Support sqlite3_db_cacheflush #145

Open
mitar opened this issue Jan 2, 2024 · 5 comments
Open

Support sqlite3_db_cacheflush #145

mitar opened this issue Jan 2, 2024 · 5 comments

Comments

@mitar
Copy link

mitar commented Jan 2, 2024

It would be great to be able to force flushing cache to disk using sqlite3_db_cacheflush, but it does not seem to be supported.

@anacrolix
Copy link
Contributor

I'm curious what your use case is for this, can you share?

@mitar
Copy link
Author

mitar commented Jan 3, 2024

I am writing a benchmarking tool to compare various key/value stores and I am also using Sqlite as such. And I would like to be able to force flush at various points during the benchmark so that I can measure how much data does it consume on the disk at that point. Many other key/value stores support some type of "sync" or "flush" operation.

@anacrolix
Copy link
Contributor

@mitar I don't suppose you'd be interested in benchmarking https://github.com/anacrolix/possum? Are you doing cache implementations too (or you could just switch off the cache part)?

@mitar
Copy link
Author

mitar commented Jan 3, 2024

@anacrolix This looks great and I was also wondering why people do not use FS for key/value more, especially because I am also interested in supporting large values. But currently I am focusing on Go ecosystem, so Possum (written in Rust) seems to be out of scope.

@anacrolix
Copy link
Contributor

It has first class Go bindings as I actually use it from Go. This is off topic to this repo, so I'll email you directly.

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