-
Notifications
You must be signed in to change notification settings - Fork 278
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
[spike] rocksdb investigation #8534
Comments
Last attempt to use rocksDb as teku database ran into issues of high disk usage. I've made an attempt to use teku with rocks on holesky and have already experienced high disk usage which may be related to the usage of some outdated default or require further tweaks to the db config. Further tweaks might be required to get the best performance out of rocksdb. For now I'm borrow some of the battle tested configs used in the besu project. I'll add more details once more conclusive numbers come up from the tests. |
Flushing some of the latest attempts and findings: 1- The simple upgrade of RocksDb to 9.5.2 seems to be fairly stable using the current configs with the only cons being the database size which roughly doubles the size when compared to what we have currently with LevelDb. 2- Tested a few tweaks up until commit 90ef567 Teku process gets OOM killed every few minutes.
I've spun up instances with 32GB to test the previous version and noticed that memory consumption is growing further (currently sitting at 13GB) for the teku-node process which kind of indicates that the off heap memory is increasing way above than expected since we set-Xmx5g for those instances. Currently testing a version disabling compression: fa9270e And reducing cache to it's original size: db412bd |
Reducing cache to the previous default has brought nodes to a stable state: memory is slightly higher than nodes on LevelDb (roughly 1GB higher with rocks) Metrics have also shown some improvements in GC time. |
Upgrade scenario has been tested and it doesn't introduce any issues/regression. |
The text was updated successfully, but these errors were encountered: