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

Suggest right disk size requirement for base node #256

Closed
DSdatsme opened this issue May 13, 2024 · 2 comments
Closed

Suggest right disk size requirement for base node #256

DSdatsme opened this issue May 13, 2024 · 2 comments

Comments

@DSdatsme
Copy link

Please help in recommending the right disk size for booting up a new base node from scratch.

  1. Disk size mentioned in the repo which is 4TB and docs i.e. 2.5TB is inconsistent

  2. Currently the snapshot size for mainnet is 3.4TB in zip. That means if someone wants to boot up a new base node, they would need at least 7TB of disk space, 3.5TB for zip download, and at least 3.5TB for extracting the data.

This means to do this efficiently and make it future-proof, do we have to boot up a server with a 10TB disk? or am I doing something wrong?

@nooperpudd
Copy link

just very simple, downloading and extracting
export LATEST=$(curl https://base-snapshots-mainnet-archive.s3.amazonaws.com/latest) && wget https://base-snapshots-mainnet-archive.s3.amazonaws.com/${LATEST} -O - | tar -xzvf - -C /data/base

@wbnns
Copy link
Contributor

wbnns commented May 23, 2024

@DSdatsme

Heya! Thanks for raising this point; opened a PR on both repositories to update this to be more explicit:

@wbnns wbnns closed this as completed May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants