Hardware Recommendations
To help with determining the proper hardware for node running, here are some concepts and recommendation to assist with resource planning.
vCPUs are equal to the amount of "Threads" (not cores) your CPU supports.
Example: 8 Threads = 8 vCPUs
We are recommending only using NMVe since fast drives are best for serving RPC requests. SSDs may cause less revenue and add to more frequent jailings for Pocket nodes.
When considering drive speeds, IOPS is the metric to consider. The higher the IOPS the faster that drive can perform random reads and writes, which results in greater performance, especially when running many nodes on a single drive.
Too many nodes running on a single drive can cause a degradation in performance. We have internally tested Node Pilot with 5 chain nodes and 5 POKT Validators on a single Gen3 NVMe drive with great performance. Some users have reported more nodes on a single drive with success, but your mileage may vary depending on your hardware and node selection.
With multiple NVMe drives, we've successfully tested up to 12+ POKT Validators on one Gen3 NVMe drive while having chain nodes on another drive.
When considering RAID, only use RAID 0 since RAID 1 greatly decreases drive IOPS.
Here are the suggested hardware specs for nodes being used on the Pocket Network. These are primarily pulled from official sources (when available).
Blockchain storage requirements grow with time. For best practice you should expect each blockchain to increase their storage requirements by 50% to 100% per year.
Node | vCPUs | RAM | NVMe Storage |
4 to 8
NOTE: plan hardware for 4 vCPUs per node, but when creating the node allocate 16. This will allow nodes extra resources to close app large session. | 20GB | 600GB | |
8 | 16GB | 1TB | |
4 | 8GB | 500GB | |
8 | 32GB | 2TB | |
8* | 16GB | 2TB | |
6* | 8GB | 45GB | |
16* | 32G* | 6TB | |
16 | 16 | 6TB | |
6* | 8GB* | 400GB |
* Have been modified to reflect the advice from experienced Pocket node runners
Last modified 3mo ago