docs(readme): Add additional recommended specs for running a node #307
Conversation
✅ Heimdall Review Status
|
README.md
Outdated
| @@ -33,7 +33,10 @@ We recommend you have this hardware configuration to run a node: | |||
|
|
|||
| - a modern multi-core CPU with good single-core performance | |||
| - at least 16 GB RAM (32 GB recommended) | |||
| - a high performance SSD drive (NVME recommended) with at least 750GB (full node) or 4.5TB (archive node) free | |||
| - a locally attached NVMe SSD drive | |||
| - adequate storage capacity to accommodate both the [snapshot restoration process](http://base.org/tutorials/run-a-base-node/#snapshots) (if restoring from snapshot) and chain data, ensuring a minimum of (2 \* current_chain_size) + snapshot_size + 20%\_buffer | |||
There was a problem hiding this comment.
curious why 2 * current_chain_size? We already have 20% buffer specified
There was a problem hiding this comment.
FYI, the specified URL returns 404. Found: https://docs.base.org/tutorials/run-a-base-node/#snapshots instead.
There was a problem hiding this comment.
@0x00101010 I have seen feedback where people do not have enough space when working with the chain data + snapshot in their local environment so wanted to try to add additional guidance here to hopefully avoid this situation. IMO, I think only the 20% buffer will not provide ample time before encountering disk space issues alongside growth of the chain; PLMK if you think something else might be preferable here 👍
@sameersubudhi Thanks for catching this; I've dropped this URL -- alongside the typo it looks like NextJS isn't loading the page client side in time to render it correctly with the page anchor
There was a problem hiding this comment.
@wbnns Make sense! In this case, can we give 2 recommendations, 1 as minimum (which we call out that it is just barely enough), and 1 recommended with 2 * current_chain_size indicating that it gives people the capability to handle chain growth?
The worry from me is that if user should make their own decision about how many buffer they want to have (cost wise, etc) and we can just give them enough information to make the decision
cb-heimdall
dismissed
anikaraghu’s stale review
Approved review 2222409524 from anikaraghu is now dismissed due to new commit. Re-request for approval.
Add additional clarity regarding hardware requirements when running a node (specifically with regard to hard drive specifications)