Skip to content

feat(book): node sizes (archive, full, pruned) #4344

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.

Sign up for GitHub

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

Merged
shekhirin merged 2 commits into from
Aug 24, 2023
Merged

feat(book): node sizes (archive, full, pruned) #4344

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
804fec4
feat(book): pruning sizes
shekhirin Aug 24, 2023
742d176
fix my english
shekhirin Aug 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions book/installation/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,11 @@ Prior to purchasing an NVMe drive, it is advisable to research and determine whe

### Disk

There are multiple types of disks to sync Reth, with varying size requirements, depending on the syncing mode:
There are multiple types of disks to sync Reth, with varying size requirements, depending on the syncing mode.
As of August 2023 at block number 17.9M:

* Archive Node: At least 2.1TB is required (as of July 2023, at block number 17.7M)
* Full Node: TBD
* Archive Node: At least 2.1TB is required
* Full Node: At least 1TB is required

NVMe drives are recommended for the best performance, with SSDs being a cheaper alternative. HDDs are the cheapest option, but they will take the longest to sync, and are not recommended.

Expand Down
28 changes: 28 additions & 0 deletions book/run/pruning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,34 @@ To run Reth as a pruned node configured through a [custom configuration](./confi
modify the `reth.toml` file and run Reth in the same way as archive node by following the steps from
the previous chapter on [how to run on mainnet or official testnets](./mainnet.md).

## Size

All numbers are as of August 2023 at block number 17.9M for mainnet.

### Archive

Archive node occupies at least 2.1TB.

You can track the growth of Reth archive node size with our
[public Grafana dashboard](https://reth.paradigm.xyz/d/2k8BXz24k/reth?orgId=1&refresh=30s&viewPanel=52).

### Full

Full node occupies 1TB at the peak, and slowly goes down to 920GB.

### Pruned

Different parts take up different amounts of disk space.
If pruned fully, this is the total freed space you'll get, per part:

| Part | Size |
|--------------------|-------|
| Sender Recovery | 70GB |
| Transaction Lookup | 140GB |
| Receipts | 240GB |
| Account History | 230GB |
| Storage History | 680GB |

## RPC support

As it was mentioned in the [pruning configuration chapter](./config.md#the-prune-section), there are several parts
Expand Down