From 24a21d0ba65a9d34836d8229466dae62e673935e Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Tue, 25 May 2021 23:22:26 +0000 Subject: [PATCH] docs: Add RPC node HW recommendations (#17490) (cherry picked from commit 64bfc14a75671e4ec3fe969ded01a599645080eb) Co-authored-by: Trent Nelson --- docs/src/running-validator/validator-reqs.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/src/running-validator/validator-reqs.md b/docs/src/running-validator/validator-reqs.md index 03990bdc54..fc1559a06e 100644 --- a/docs/src/running-validator/validator-reqs.md +++ b/docs/src/running-validator/validator-reqs.md @@ -38,6 +38,20 @@ transaction for each block the validator agrees with, which can cost up to - Motherboard and power supply speced to add one or more high-end GPUs in the future suggested +### RPC Node Recommendations +The [hardware recommendations](#hardware-recommendations) above should be considered +bare minimums if the validator is intended to be employed as an RPC node. To provide +full functionality and improved reliability, the following adjustments should be +made. + +- CPU + - 16 cores / 32 threads, or more +- RAM + - 256 GB, or more +- Disk + - Consider a larger ledger disk if longer transaction history is required + - Accounts and ledger should not be stored on the same disk + ## Virtual machines on Cloud Platforms While you can run a validator on a cloud computing platform, it may not