Last active
April 11, 2021 06:31
-
-
Save bensig/b2a8ec7e17f6a0d0a5432e5242fd2ade to your computer and use it in GitHub Desktop.
EOSIO Block Producer Hardware Recommendations
This file contains hidden or 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
There are a few roles for servers - API, P2P, HYPERION, and PRODUCER | |
# Producer Role | |
EOSIO block producers are mostly single threaded for processing transactions. | |
...so normally I would never recommend using desktop hardware in place of server hardware, but in the case of producer nodes where clockspeed is king and you can mitigate risk by running a failover node - it's not THAT bad. | |
You might use a Z490 PRIME mobo with a i9-10900k, water cooling, and 32GB RAM (can't use ECC ram. another drawback to using desktop hardware.) | |
I'd recommend a enterprise SSD | |
1 out of 6 EVO SSDs have failed completely | |
Could have been a faulty one. could have been a meltdown. it was only running for 2 months | |
Also, there are enterprise SSDs with pricing on par with EVOs now so the reliability is worth it | |
## Other recommendations: | |
I7-7700k @ 4.5GHz , OS and /state on nvme and /blocks on SATA .. for our producer | |
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz | |
primary on i9, backup on E5-1620 v4 @ 3.50GHz | |
We're using the 10900K i9 I believe (for producing) | |
Normally a producer goes with nvme or ssd, 480GB or so. The block logs and state history are normally stored on HDD | |
Hyperion - depends on the network. But 12x HDD drives on a RAID controller work fine for Wax, which is pretty busy recently | |
And no aws or gcp, everything baremetal |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment