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

archive node consumes a lot of memory with --config-file flag #15618

Open
ghost-not-in-the-shell opened this issue May 8, 2024 · 0 comments
Open

Comments

@ghost-not-in-the-shell
Copy link
Member

When start an archive node the first time with --config-file flag, it would try to add the genesis accounts, and this would consumes a lot of memory. For example, in short-epoch dry run network, the memory usage of the archive node takes about 50 GB of memory and the initialization process takes about an hour.

This --config-file flag is optional. In theory, it's not needed for migrated database, because accounts in the fork genesis ledger has already been populated by migration.

Suggestion: we should add this to the doc, so that user would not be surprised by the high memory usage.

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

No branches or pull requests

1 participant