status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
nimbus-eth2/docs/the_nimbus_book/src/hardware.md

24 lines
970 B
Markdown
Raw Normal View History

book edits (#3903) * Reorganise menu, putting tabs on top * Use tabs for specific content * cleanups and consistency edits
2022-07-24 20:13:47 +00:00
# System requirements
add mainnet preparation guide (#2022)
2020-11-16 10:22:29 +00:00
book updates (#3763) * systemd: use same service file as package * systemd: recommend setting up a user * clean up obsolete / ephemeral notes * eth1 -> execution, in many places * clean up docker instructions to match the experience of running the runner script * add basic instructions / links for execution clients other than geth * clear a few more references to JSON-RPC, update to REST * update hardware requirements with execution client extras * start talking about merge requirements (this needs a dedicated page) * note that binaries do exist, where relevant * list gitcoin under donations * update syncing docs * `NOT` is for `NOTICE` in logs * update rpi hardware recommendations * prevent automatic doppelganger restarts in systemd service file
2022-06-17 15:28:13 +00:00
The recommended system requirements for running the Nimbus beacon node are:
cp (#3053)
2021-11-05 10:33:28 +00:00
book edits (#3903) * Reorganise menu, putting tabs on top * Use tabs for specific content * cleanups and consistency edits
2022-07-24 20:13:47 +00:00
| What | Recommended |
| ---------- | ------ |
note 8GB requirement is for building; fix macOS supported version (#4594)
2023-02-06 07:21:11 +00:00
| Operating system | Linux [64-bit](https://en.wikipedia.org/wiki/64-bit_computing), Windows 64-bit, macOS 11+ |
| Memory | 4GB (running) or 8GB (building) |
book edits (#3903) * Reorganise menu, putting tabs on top * Use tabs for specific content * cleanups and consistency edits
2022-07-24 20:13:47 +00:00
| Disk space | 200GB |
| Network | Reliable broadband |
add mainnet preparation guide (#2022)
2020-11-16 10:22:29 +00:00
Update "Getting started" part of the book (#4938) * refactor index.md * move philosophy.md into index.md * clean up the 'getting started' topic move how-to's to the how-to section * cleaner titles * move prerequisites to the install.md page * hardware.md: small refactor * improve quick-start.md * refactor eth1.md * refactor validating guide * reverse the order of BN and LC in the table * pi-guide.md: minor edit * Apply suggestions from code review Co-authored-by: tersec <tersec@users.noreply.github.com> * make link texts more concrete * remove comparison to other clients * add some more explanations to `build.md` * change 'days' to 'hours' --------- Co-authored-by: tersec <tersec@users.noreply.github.com>
2023-06-09 23:06:01 +00:00
### Execution client
add mainnet preparation guide (#2022)
2020-11-16 10:22:29 +00:00
Update "Getting started" part of the book (#4938) * refactor index.md * move philosophy.md into index.md * clean up the 'getting started' topic move how-to's to the how-to section * cleaner titles * move prerequisites to the install.md page * hardware.md: small refactor * improve quick-start.md * refactor eth1.md * refactor validating guide * reverse the order of BN and LC in the table * pi-guide.md: minor edit * Apply suggestions from code review Co-authored-by: tersec <tersec@users.noreply.github.com> * make link texts more concrete * remove comparison to other clients * add some more explanations to `build.md` * change 'days' to 'hours' --------- Co-authored-by: tersec <tersec@users.noreply.github.com>
2023-06-09 23:06:01 +00:00
In addition to the beacon node, you will need to run an [execution client](./eth1.md).
Check the documentation of the client of choice and add them to the above requirements.
Broadly, to run both an execution and a consensus client on the same machine, we recommend a **2 TB** SSD and **16 GB RAM**.
### Minimal requirements
Nimbus has been optimized to also run well on hardware significantly less powerful than the recommended system requirements — the more validators you run on the same node, the more hardware resources and network bandwidth will it will use.