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): more precise disk requirements (#3838)

Browse Source
This commit is contained in:
Alexey Shekhirin
2023-07-18 21:28:29 +02:00
committed by GitHub
parent 5ad9b32cbc
commit 0e05085e55
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
book/installation/installation.md
View File

@ -14,12 +14,12 @@ The hardware requirements for running Reth depend on the node configuration and
The most important requirement is by far the disk, whereas CPU and RAM requirements are relatively flexible. The most important requirement is by far the disk, whereas CPU and RAM requirements are relatively flexible.
| | Archive Node | Full Node | | | Archive Node | Full Node |
|-----------|----------------------------------------|-------------------------------------| |-----------|---------------------------------------|-------------------------------------|
| Disk | At least 2TB (TLC NVMe recommended) | TBD | | Disk | At least 2.1TB (TLC NVMe recommended) | TBD |
| Memory | 8GB+ | 8GB+ | | Memory | 8GB+ | 8GB+ |
| CPU | Higher clock speed over core count | Higher clock speeds over core count | | CPU | Higher clock speed over core count | Higher clock speeds over core count |
| Bandwidth | Stable 24Mbps+ | Stable 24Mbps+ | | Bandwidth | Stable 24Mbps+ | Stable 24Mbps+ |
#### QLC and TLC #### QLC and TLC
@ -35,12 +35,12 @@ Prior to purchasing an NVMe drive, it is advisable to research and determine whe
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:
* Archive Node: At least 2TB is required to store * Archive Node: At least 2.1TB is required (as of July 2023, at block number 17.7M)
* Full Node: TBD * Full Node: TBD
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.
At the time of writing, syncing an Ethereum mainnet node to block 17.4M on NVMe drives takes about 50 hours, while on a GCP "Persistent SSD" it takes around 5 days. As of July 2023, syncing an Ethereum mainnet node to block 17.7M on NVMe drives takes about 50 hours, while on a GCP "Persistent SSD" it takes around 5 days.
> **Note** > **Note**
> >