A Java server rarely runs out of memory all at once. It gets slower first, and the official manual names the typical symptom: higher CPU usage due to garbage collection.
What you'll notice
- Memory in the panel sits close to your plan's limit for long periods.
- CPU usage rises without more players joining.
- The server stutters in regular bursts while Java frees memory.
- In the worst case, the server stops with an out-of-memory error in the console.
What to do
- Lower the view distance
It's the main driver of RAM usage, according to the manual.
- Review heavy mods
Remove mods you don't use; each one takes memory.
- Move to a bigger plan
If the server is simply busier than its plan, upgrading keeps your files and adds headroom.
About this guide: An original guide from the EnduranceNodes team, written for the servers we host. If a step no longer matches what you see, tell us and we will update it.
