Skip to content
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

genesis.json of 10GB cause 200GB ram usage #17773

Closed
alpha-omega-labs opened this issue Sep 16, 2023 · 6 comments
Closed

genesis.json of 10GB cause 200GB ram usage #17773

alpha-omega-labs opened this issue Sep 16, 2023 · 6 comments

Comments

@alpha-omega-labs
Copy link

Summary

Hello,
We have quite an issue in GenesisL1 with extensive RAM usage during initialization of node from exported genesis.json with state. 10GB file cause up to 200GB RAM utilization
Is there a way to optimize it? There been some works regarding genesis,json streaming, is it implemented opt in sdk v0.46.15?
Thank you!

Problem Definition

No response

Proposed Feature

genesis.json efficient processing

@tac0turtle
Copy link
Member

Newer versions of the cosmos sdk will have a reduced foot print. Have you tried using 0.50?

@alpha-omega-labs
Copy link
Author

We have ethermint and probably there are no chains working with 0.5 and ethermint.
You think that 10GB genesis.json will work well in v0.5 of sdk, in terms of ram and cpu.
Maybe you know ethermint implementations with v 0.5?
Thank you

@alpha-omega-labs
Copy link
Author

Overall this seems to be related: #11601

@alpha-omega-labs
Copy link
Author

Newer versions of the cosmos sdk will have a reduced foot print. Have you tried using 0.50?

0.47 has it?

@alpha-omega-labs
Copy link
Author

the way genesis.json processed at versions at least < 0.46 of SDK make it unusable for starting new chain with big state (big genesis.json).

@tac0turtle
Copy link
Member

closing this as duplicate here #16915

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants