We have tried to set up a geth node on a droplet with 4CPU/8RAM+attached volume for the geth DB, but it’s been for more than a week in a healing state. According to this done - https://eth-docker.net/docs/Usage/ResourceUsage/#initial-sync-times - that might be due to a low IOPS. Does anyone has experience in running snap/full geth node on a DO droplet?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Hi there,
Have you tried using a storage-optimized Droplet for this?
The Storage-Optimized Droplets come with NVMe SSD storage which should give better IOPS.
If you are still seeing the issue, could you share the output of the command listed in that tutorial that you’ve shared regarding testing the read/write speed?
Best,
Bobby