Best Practices + 2 broken links fixed #47
+232
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RaekwonIII
reviewed
Apr 18, 2025
| - **CPU frequency is a major factor**. Fast cores with moderate-to-high core count are the recipe. Ensure each server can turbo boost to high frequency, yet avoid agressive overclocking. | ||
| - **Disk and Redundancy:** NVMe SSDs are mandatory. Many use RAID1 mirroring or have failover nodes ready in case of disk failure. Recommended to use ext4 if unsure about ZFS's complexities. Improving read/write speed has one of the greatest impacts. | ||
| - **RAM Considerations:** Usually RAM is not the limiting factor. Abundant RAM enables disk caching for the execution client database – reducing disk reads and writes. ECC memory is advisable to protect against bit flips in long-running servers. | ||
| - **Form Factor and Data Center:** Run on a mix of bare metal servers in colocation data centers and cloud VM instances. In either case, redundancy across hardware and geographic distribution is a best practice. |
There was a problem hiding this comment.
"a mix of" sounds a bit misleading. It almost sounds like they should have SSV node on bare metal, CL on cloud, and EL somewhere else. Can you be more specific?
| - **Hardware Resources:** Adequate CPU, sufficient RAM, and fast, reliable storage are necessary. | ||
|
|
||
| ## **Major impact** | ||
| More obvious, more impactful. |
There was a problem hiding this comment.
"more obvious, more impactful"...peanuts? stones?
I know it's kinda obvious, but make this a one-liner description...
| *** | ||
|
|
||
| ## **Minor impact** | ||
| Less obvious, less impactful. |
| ``` | ||
| echo 1024 | sudo tee /sys/block/nvme0n1/queue/nr_requests | ||
| ``` | ||
| - [Disable `atime` feature](https://ethdocker.com/Usage/LinuxSecurity/#noatime) to bump up the performance and increase the lifetime of your SSD. |
There was a problem hiding this comment.
Goddamn that's good research! I did not know about these 3, at all...
| **Considerations:** | ||
| - **Besu and Teku** were reported to be not a great fit together, with SSV specifically. | ||
| - **Erigon (EL)** has the largest ledger in ELs, is heavy on RAM usage, and lower sync speed. For home setups with limited resources it can cause issues. | ||
| - **Nimbus (CL)** performs well on a low validator count, however, post ~250 it won't be able to scale properly and you might have to switch clients. |
There was a problem hiding this comment.
"...with more than ~250..."
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
docs/operators/operator-onboarding/verified-operators.mdthe Verified Operator list linkdocs/operators/operator-node/node-setup/enabling-dkg/start-dkg-node/README.mdlink to Manual Configuration page