-
Notifications
You must be signed in to change notification settings - Fork 609
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
Make Export Less RAM Intensive (IAVL Changes) #2953
Comments
Can I have some questions ?
|
This refers to cms Store's Write() right ? Can you explain this more ? |
I am going to have to have a separate conversation with Dev to get a better / more concrete understanding of the best way forward with this. This might have to happen later this week sadly |
seems like the non-atomic writes is explained here |
@czarcas7ic, do we have any update on this? |
I sadly do not have context on this, @ValarDragon would you be able to write something out in order to allow @catShaark to pick up this task? |
Basically make key formats we write to disk follow
This is entirely unrelated
Basically just change the batch.set & batch.writeSync usage in IAVL, to write in many smaller batches. E.g. write every 1MB atomically, don't keep growing the batches. We already have tooling for detecting when we've completed the final write, the whole thing should not be atomic, it should just be possible to safely automatically rollback / wipe latest version. |
@catShaark I would love to work with you on smaller batch writing. Would you be interested in working together? |
yesss, just tell me what to do |
why not streaming of genesis? agree that batching would help but also streaming would be the correct solution |
Unneeded due to in-place testnet |
Background
It currently takes VMs with 64GB of RAM to export/import full state exports. Some basic IAVL improvements can be done to improve this performance.
Suggested Design
Acceptance Criteria
The text was updated successfully, but these errors were encountered: