π Maximizing Uptime and Performance
Easyβ
- Connect your validator node to your router directly via a LAN cable. WIFI connection is too unstable to perform your validator duties in a timely manner.
- If you are only using an integrated modem + router provided by your ISP, you might find that connecting a validator node to it degrades the quality of service for all other usage. If so, get a good router and connect it downstream to your modem. Then connect all devices to this new router instead.
- Update your clients in a timely manner as these usually come with performance improvement fixes
- Create a new server on Discord to receive alerts on new releases and patches of your execution layer and consensus layer clients. Keep this channel clean.
- Set alerts from the announcement channels to your own server
- Set up the monitoring & alerting services so that you are alerted on any downtime promptly
- During normal operations, configure your clients to restart themselves automatically if they go down. This is in accordance to this guide
- Prune your execution layer clients before you reach <300 GB of available space
- Check for scheduled sync committee duties here and block proposal duties here before starting the pruning process
Advancedβ
- ETH Docker performance tuning tips
- Switch the timekeeping service from the default NTP service to Chrony
- Configure swapiness=1 or disable swap entirely if you have 32 GB or more RAM
- Configure noatime on your disk
- Community-contributed performance tuning tips
- Configure Quality of Service (QoS) on your router to prioritise your validator node
- Maintain your own SOPs table for dealing with the various scenarios of downtime, including edge cases. Improve on this over time based on your own setup environment.