Clarification on node storage requirements
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- documentation, infrastructure
Research direction
Start with docs/base-chain/node-operators/performance-tuning.mdx at the linked formula and review the snapshot and chain-size sources cited there. Verify how Reth Archive storage is calculated, including whether the snapshot must remain persisted after decompression. Done means the questions are answered and the documentation gives an unambiguous requirement.
Written by the indexing model from the issue text.
Description
In various pages, this formula is presented to compute node size:
(2 × chain_size) + snapshot_size + 20% buffer
According to the links in this page, the values of the variables for a Reth Archive setup are:
- snapshot_size = 1.83 TB (link)
- chain_size = 8.88 TiB, or 9.76 TB (link, assuming that it's the value of "Reth Mainnet Archive" that should be used)
Which gives a total NVMe storage requirement of (2*9.76+1.83)*1.2 TB, which is 25.62 TB
I have the following questions:
- Is this computation correct?
- Is the presence of the snapshot size in the formula only necessary to account for its initial download+de-compression? Meaning it could be skipped if we download and uncompress without persisting the archive
- Dominant language
- JavaScript
- Stars
- 337
- Forks
- 798
- Avg merge
- 7h 24m
- Merged PRs (30d)
- 51
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from base/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·
-
bug p1 tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100