mirror of
https://github.com/hl-archive-node/nanoreth.git
synced 2025-12-06 19:09:54 +00:00
feat(book): node sizes (archive, full, pruned) (#4344)
This commit is contained in:
@ -33,10 +33,11 @@ Prior to purchasing an NVMe drive, it is advisable to research and determine whe
|
|||||||
|
|
||||||
### Disk
|
### 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)
|
* Archive Node: At least 2.1TB is required
|
||||||
* Full Node: TBD
|
* 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.
|
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.
|
||||||
|
|
||||||
|
|||||||
@ -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
|
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).
|
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
|
## RPC support
|
||||||
|
|
||||||
As it was mentioned in the [pruning configuration chapter](./config.md#the-prune-section), there are several parts
|
As it was mentioned in the [pruning configuration chapter](./config.md#the-prune-section), there are several parts
|
||||||
|
|||||||
Reference in New Issue
Block a user