-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Feature request: Make sqlite parameters user-configurable #3242
Comments
I'm curious if anyone has done some benchmarks or tests about these settings. |
@mlusetti > I'm curious if anyone has done some benchmarks or tests about these settings. SQLite is extremely robust by default and there is a lot of research available of it's capabilities and limitations, This document describes limitations of SQLite (the maximum length of a string or blob, the maximum size of a database, the maximum number of tables in a database, etc.) and how these limits can be altered at compile-time and run-time. SQLite is safe to use in multi-threaded programs. This document provides the details and hints on how to maximize performance. Unlock Notify → The "unlock notify" feature can be used in conjunction with shared cache mode to more efficiently manage resource conflict (database table locks). |
Hi Brett, I'm well aware of the capabilities of SQLite and have read some papers, even some you linked. |
If it's easier, I'd be interested in injecting my own sqlite connection into the bootstrap process. One use case would be configuring the sqlite params. Another would be to use something like https://github.com/psanford/donutdb or https://rqlite.io |
It would be great if certain sqlite parameters, e.g.
cache_size
were user-configurable (or alternatively, auto-adjusted / dynamic). These parameters usually depend on the current hardware and the type of work the given pb instance will execute.The text was updated successfully, but these errors were encountered: