From b65e808ebf215b3546b749188e8fe73f5656aa76 Mon Sep 17 00:00:00 2001 From: Alexey Shekhirin Date: Thu, 24 Aug 2023 16:30:06 +0100 Subject: [PATCH] feat(book): node sizes (archive, full, pruned) (#4344) --- book/installation/installation.md | 7 ++++--- book/run/pruning.md | 28 ++++++++++++++++++++++++++++ 2 files changed, 32 insertions(+), 3 deletions(-) diff --git a/book/installation/installation.md b/book/installation/installation.md index a7fd324bf..0dd779cb2 100644 --- a/book/installation/installation.md +++ b/book/installation/installation.md @@ -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. diff --git a/book/run/pruning.md b/book/run/pruning.md index 81c55e826..48382f000 100644 --- a/book/run/pruning.md +++ b/book/run/pruning.md @@ -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