jleony/nanoreth
1
0
Fork 0
mirror of https://github.com/hl-archive-node/nanoreth.git synced 2025-12-06 10:59:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Alexey Shekhirin
2023-08-24 16:30:06 +01:00
committed by GitHub
parent 97913049df
commit b65e808ebf
2 changed files with 32 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
book/run/pruning.md
View File

@ -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