Spotlight: Solana validator and hardware requirements

Summary

In this discussion, experts from the Solana Foundation and Latitude explore the intricacies of running Solana validators and RPC servers. They cover key differences between validators (which vote on blocks) and RPCs (which handle API requests), along with the hardware requirements for both. Recommendations include high-frequency AMD CPUs, large amounts of RAM (128 GB for validators, 500 GB to 1 TB for RPCs), and NVMe drives. The conversation also delves into bandwidth needs, geographical considerations, and the advantages of bare metal servers over virtual machines for performance. The experts also touch on emerging technologies like ARM and next-gen AMD processors.

Takeaways

• 😀 Validators on the Solana network participate in consensus and vote on blocks, while RPC nodes handle API requests but do not vote.
• 😀 High-frequency CPUs, such as AMD's 3rd generation processors, are recommended for both Solana validators and RPC nodes.
• 😀 A validator’s primary function is to validate and vote on blocks, while an RPC node provides access to blockchain data through API requests.
• 😀 Solana validators require at least 128 GB of RAM, with 256 GB being the optimal configuration for high performance.
• 😀 RPC nodes, which serve API requests for Solana programs, need significantly more RAM—at least 500 GB, with 1 TB recommended for comprehensive indexing.
• 😀 Bare metal servers are preferred over virtual machines for running Solana validators and RPC nodes due to better performance with high-frequency CPUs and less virtualization overhead.
• 😀 Solana validators use RAM disks for storing accounts to avoid wearing out physical hard drives due to high transaction volume.
• 😀 NVMe PCIe Gen 4 SSDs are recommended for RPC nodes to handle large amounts of data while maintaining fast read/write speeds.
• 😀 The bandwidth required for a Solana validator can range from 150 to 300 TB of egress traffic per month, depending on stake and location.
• 😀 RPC nodes typically use about 50 TB of egress traffic per month, with traffic increasing based on API request volume, potentially reaching 400 TB.
• 😀 Physical location of Solana validators is crucial for performance, with nodes often set up in regions with high stake concentrations, like the East Coast of the U.S., Western Europe, and Japan.

Q & A

What is the main difference between a validator and an RPC node on the Solana network?

The main difference is that a validator actively participates in the network's consensus by voting on blocks, while an RPC node only serves API requests and does not participate in the consensus process. Validators vote on blocks and incur costs, whereas RPCs simply provide data access without casting votes.

What hardware specifications are recommended for running a Solana validator?

For Solana validators, a high-frequency CPU is recommended, typically a third-generation AMD processor. The minimum RAM for a validator is 128 GB, with 256 GB being ideal for stable performance. The validator should also use fast storage like NVMe drives and preferably store blockchain accounts in RAM, using RAM disks to ensure better performance and longer hardware lifespan.

Why is it important to use bare-metal servers instead of cloud-based virtual machines (VMs) for Solana validators?

Bare-metal servers are preferred because they provide consistent, high-performance hardware with high clock speed CPUs, which are crucial for Solana's high-throughput requirements. Cloud VMs often over-commit resources and use CPUs optimized for virtualization, which may not provide the necessary frequency and performance for a high-performance blockchain network like Solana.

What role does RAM play in the performance of Solana validators and RPCs?

RAM is critical for both validators and RPCs. Validators use RAM disks to store accounts, which improves performance and prevents wear on hard drives. RPC nodes, on the other hand, need substantial memory to handle data requests, with 500 GB to 1 TB of RAM often required to serve API calls and index Solana’s blockchain data efficiently.

What bandwidth requirements should be considered when setting up a Solana validator?

Validators should be equipped with a minimum of **10 Gbps** network interfaces to handle traffic spikes. Average validators can consume between **150 TB to 300 TB** of monthly egress traffic depending on their stake, while RPC nodes typically use **50 TB to 400 TB** of data per month based on API requests. The recommended sustained bandwidth is around **300 Mbps**, but higher throughput is essential during peak network activity.

Why are third-generation AMD CPUs recommended for Solana validators and RPCs?

Third-generation AMD CPUs are preferred because they offer high clock speeds and are well-suited to handle Solana's transaction-heavy operations. Older AMD processors and Intel CPUs, on the other hand, struggle with the performance demands of the network, especially when it comes to frequency, which is critical for maintaining consensus.

How much RAM is needed for an RPC node on the Solana network?

RPC nodes typically require **500 GB to 1 TB of RAM**, depending on the volume of requests and data indexing they need to handle. For providing API requests related to specific Solana programs, a minimum of 500 GB is recommended, but for indexing all Solana data, **1 TB of RAM** is ideal.

What are the potential risks of using hard drives instead of RAM disks in Solana validators?

Using hard drives instead of RAM disks can significantly reduce performance and shorten hardware lifespan. Hard drives, especially under heavy load, wear out quickly, as they are not designed for the high-speed, high-volume data operations required by Solana validators. RAM disks provide faster access and avoid these issues.

How does the physical location of a validator node affect its performance?

The physical location of a validator node is important because it impacts its network latency and ability to attract staking rewards. Validators typically set up nodes close to regions with high concentrations of staked tokens, such as the East Coast of the US, Western Europe, and Japan. Proximity to these staking pools reduces block skipping and improves performance.

What bandwidth is needed for Solana RPC nodes handling high amounts of traffic?

Solana RPC nodes require significant bandwidth, with some nodes using up to **400 TB of egress traffic per month** depending on the level of API request activity. It’s essential to have a high-capacity network setup, ideally with **10 Gbps interfaces**, to handle large amounts of incoming and outgoing data without bottlenecks or throttling.