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

docs(book): update node size numbers (#7638)

Browse Source
This commit is contained in:
Alexey Shekhirin
2024-04-14 19:19:53 +01:00
committed by GitHub
parent 3e8d5c69cf
commit cfbebc1595
2 changed files with 17 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
book/run/pruning.md
View File

@ -48,14 +48,14 @@ RUST_LOG=info reth node \
## Size
All numbers are as of October 2023 at block number 18.3M for mainnet.
All numbers are as of April 2024 at block number 19.6M for mainnet.
### Archive Node
Archive node occupies at least 2.14TB.
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).
[public Grafana dashboard](https://reth.paradigm.xyz/d/2k8BXz24x/reth?orgId=1&refresh=30s&viewPanel=52).
### Pruned Node
@ -64,15 +64,15 @@ If pruned fully, this is the total freed space you'll get, per segment:
| Segment | Size |
| ------------------ | ----- |
| Sender Recovery | 75GB |
| Transaction Lookup | 150GB |
| Sender Recovery | 85GB |
| Transaction Lookup | 200GB |
| Receipts | 250GB |
| Account History | 240GB |
| Storage History | 700GB |
| Account History | 235GB |
| Storage History | 590GB |
### Full Node
Full node occupies at least 950GB.
Full node occupies at least 1.13TB.
Essentially, the full node is the same as following configuration for the pruned node:
@ -100,16 +100,6 @@ Meaning, it prunes:
is completed, so the disk space is reclaimed slowly.
- Receipts up to the last 10064 blocks, preserving all receipts with the logs from Beacon Deposit Contract
Given the aforementioned segment sizes, we get the following full node size:
```text
Archive Node - Receipts - AccountsHistory - StoragesHistory = Full Node
```
```text
2.14TB - 250GB - 240GB - 700GB = 950GB
```
## RPC support
As it was mentioned in the [pruning configuration chapter](./config.md#the-prune-section), there are several segments which can be pruned