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

fix(book): broken links & missing SUMMARY.md entries (#3262)

Browse Source
This commit is contained in:
Alexey Shekhirin
2023-06-20 13:43:34 +01:00
committed by GitHub
parent c75cacf855
commit fb710e5fdb
11 changed files with 18 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
book/installation/installation.md
View File

@ -23,7 +23,7 @@ The most important requirement is by far the disk, whereas CPU and RAM requireme
### Disk
There are multiple types of disks to sync Reth, with varying size requirements, depending on the [syncing mode](../run/sync-modes.md):
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
* Full Node: TBD
@ -36,7 +36,7 @@ At the time of writing, syncing an Ethereum mainnet node to block 17.4M on NVMe
Most of the time during syncing is spent executing transactions, which is a single-threaded operation due to potential state dependencies of a transaction on previous ones.
As a result, the number of cores matters less, but in general higher clock speeds are better. More cores are better for parallelizable [stages](../developers/architecture.md) (like sender recovery or bodies downloading), but these stages are not the primary bottleneck for syncing.
As a result, the number of cores matters less, but in general higher clock speeds are better. More cores are better for parallelizable [stages](https://github.com/paradigmxyz/reth/blob/main/docs/crates/stages.md) (like sender recovery or bodies downloading), but these stages are not the primary bottleneck for syncing.
### Memory

2
book/installation/source.md
View File

@ -123,7 +123,7 @@ Rust Version (MSRV) which is listed under the `rust-version` key in Reth's
If compilation fails with `(signal: 9, SIGKILL: kill)`, this could mean your machine ran out of
memory during compilation. If you are on Docker, consider increasing the memory of the container, or use a [pre-built
binary](../binaries.md).
binary](../installation/binaries.md).
If compilation fails with `error: linking with cc failed: exit code: 1`, try running `cargo clean`.