-
Notifications
You must be signed in to change notification settings - Fork 106
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
Tune RocksDB memory usage #1486
Comments
So different users will probably get different measurements. |
Do we want to investigate this further or close it out for now? |
I don't think we can do anything about this issue right now. |
PR #1523 will help us monitor Zebra's memory usage over time, in a consistent environment. |
Analysis
We think RocksDB is the major Zebra memory user.
Here is the RocksDB memory tuning guide:
https://github.com/facebook/rocksdb/wiki/Memory-usage-in-RocksDB
We probably want to add sprout and sapling anchors, and finish transaction validation, before we try to tune memory. Those changes will increase the database size, and change data access patterns.
Unbounded block queues can also use a lot of memory, see #1389
Version
v1.0.0-alpha.0
Platform
Unknown
Description
Zebra uses 4.3 GB, but zcashd uses 1.5 GB of RAM.
The text was updated successfully, but these errors were encountered: