As our very own Turbo Geth ETH full node syncs up to the network, we can only be grateful it’s 700GB‘s~ of data rather than 5.5TB. Turbo Geth (TG) acts as “a faster, powered-up version of the long-established Geth client.” After receiving a grant in late 2018, the developers over at Turbo-Geth began experimenting on ways to speed up and improve the underlying database.What is GETH?
“Go Ethereum is one of the three original implementations (along with C++ and Python) of the Ethereum protocol. It is written in Go, fully open source and licensed under the GNU LGPL v3. See our repository and downloads section for the code!”What are the advantages and disadvantages of using Turbo GETH?
Advantages: One large pro is that the initial network sync is much faster. Database size comparisons are drastically different as well, requiring significantly less disk space than a traditional ETH node.
Disadvantages: The software is currently in a public alpha stage. There are also some RPC commands that have yet to be implemented, as seen here. Currently, there is no way to fast sync, warp sync or any other snapshot sync using Turbo GETH.
🙏Our Token Just Launched! Check it out. 🙏What are the hardware requirements for a Turbo-Geth full archive node?
When it comes to nodes, all aspects of your hardware are important. The initial sync of your node could vary drastically depending on your hardware.
Sorted most important top down.
Storage requirements for Turbo Geth nodes starts at 830GB and will likely grow from here. Play it safe and grab a 2TB SSD or more. Personally, I’m syncing to my laptop’s SSD and then will transfer the data locally to my 6TB USB attached (non-SSD) storage. In my opinion, this is the best of both worlds – cost to performance.
More info on Turbo Geth disk usage can be found here.
Internet speeds for any ETH node are important. Going back to th...