-
Notifications
You must be signed in to change notification settings - Fork 86
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
Add a way to disable caching so lightwalletd always gets data from node RPCs #480
Comments
LarryRuane
pushed a commit
to LarryRuane/lightwalletd
that referenced
this issue
May 6, 2024
This fixes issue zcash#480. Enabling this option decreases the performance of gRPCs GetBlock and GetBlockRange, but conserves disk space (the size of the database is currently around 17GB).
LarryRuane
pushed a commit
to LarryRuane/lightwalletd
that referenced
this issue
May 6, 2024
This fixes issue zcash#480. Enabling this option decreases the performance of gRPCs GetBlock and GetBlockRange, but conserves disk space (the size of the database is currently around 17GB). Note, specifying this option will also delete the existing cache (so if you start again without --nocache, the cache will need to be recreated).
LarryRuane
pushed a commit
to LarryRuane/lightwalletd
that referenced
this issue
Jun 13, 2024
This fixes issue zcash#480. Enabling this option decreases the performance of gRPCs GetBlock and GetBlockRange, but conserves disk space (the size of the database is currently around 17GB). Note, specifying this option will also delete the existing cache (so if you start again without --nocache, the cache will need to be recreated).
LarryRuane
pushed a commit
to LarryRuane/lightwalletd
that referenced
this issue
Jun 27, 2024
This fixes issue zcash#480. Enabling this option decreases the performance of gRPCs GetBlock and GetBlockRange, but conserves disk space (the size of the database is currently around 17GB). Note, specifying this option will also delete the existing cache (so if you start again without --nocache, the cache will need to be recreated).
LarryRuane
pushed a commit
that referenced
this issue
Jun 27, 2024
This fixes issue #480. Enabling this option decreases the performance of gRPCs GetBlock and GetBlockRange, but conserves disk space (the size of the database is currently around 17GB). Note, specifying this option will also delete the existing cache (so if you start again without --nocache, the cache will need to be recreated).
github-project-automation
bot
moved this from highest priority
to done
in @LarryRuane's todo
Jun 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your feature request?
It would be nice to have a way to disable the cache in lightwalletd with a config field or an environment variable so that there's no initial sync and the gRPC method are purely a proxy for the node's RPC methods.
How would this feature help you?
This could help reduce storage requirements when using lightwalletd with Zebra, including in Zebra's CI.
The text was updated successfully, but these errors were encountered: