Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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.
Hi there,
I think that this is pretty common with full nodes. Once it’s synced, the I/O load and memory usage spike hard because it’s constantly writing state and handling new blocks.
You can try adding more swap (at least 4–8GB), but it’s a band-aid. Might be better to go with a CPU-optimized Droplet.
But first, check if OOM killer is nuking the process (dmesg | grep -i kill). That will tell you if you actually just need more RAM. But it sounds like you’ll likely just need more RAM.
Let me know how it goes!
- Bobby