MINECRAFT HOSTING
GAME SERVERS
Game Panel
Client Area
by A Minecraft server that feels slow is almost never short of memory. It is failing to finish a tick in 50 ms, and the causes are entities, chunk loading, view distance and server software, roughly in that order. Fix those and a 4 GB server outperforms a badly tuned 12 GB one.
The measurement that matters is TPS, not RAM usage. Twenty ticks per second is full speed. Anything below that is the server running out of time, not out of space.
Work through it in this order
1. View distance. Every player keeps a square of chunks loaded around them. Dropping view distance from 10 to 6 cuts that area by roughly two thirds and is usually the single largest win available. Simulation distance can go lower still, because most players cannot tell the difference between a mob freezing at 6 chunks or 10.
2. Entities. Mob farms, item drops, minecarts and armour stands are all ticked. A few thousand dropped items behave exactly like a denial of service you built yourself. Cap mob spawns, clear items on a timer, and look hard at any farm running while nobody is nearby.
3. Redstone and hoppers. Hoppers poll constantly, whether or not anything is moving through them. A wall of hoppers is expensive in a way that looks like nothing at all.
4. Chunk loading. Anything keeping chunks loaded far from players costs a tick budget forever. Chunk loaders and portal-based systems are worth auditing before buying a bigger plan.
5. Server software. Paper does the same job for less than vanilla, and the difference is not marginal. Forge and Fabric add mod work on top, which is the price of the mods rather than a fault.
The memory question, answered properly
Memory becomes the constraint in exactly two situations, and both are recognisable:
java.lang.OutOfMemoryErrorin the log. Unambiguous. Buy more.- Sawtooth memory with periodic freezes. Garbage collection pauses. That is a tuning problem before it is a purchase.
Everything else that feels like lag is the tick loop. How much RAM a Minecraft server needs covers sizing and the JVM flags in detail, including why -Xms and -Xmx should be equal and why allocating your whole plan to the heap backfires.
Modded servers are a different animal
Mods load at startup and stay loaded. That has two consequences people meet the hard way:
- Idle usage is high and that is normal. A modpack that sits at 6 GB with nobody online is not broken.
- The tick cost is per-mod and cumulative. Machines, chunk loaders and world generation mods all add work every tick, and they add it whether the player who built them is online or not.
Add mods in batches so a performance drop points at something. It is the same discipline that keeps Garry's Mod and Factorio servers healthy, and the same mistake ruins all three.
What to do before buying a bigger plan
- Set view distance to 6 and simulation distance to 4. Measure.
- Clear dropped items and cap mob spawns. Measure.
- Switch to Paper if you are not on it and not modded. Measure.
- Only then look at the plan.
Our Minecraft server hosting exposes view distance, server software and the JVM flags from the panel, so each of those is a restart rather than a support ticket.
When it really is us, not you
If TPS is fine but everything feels delayed, that is latency rather than server load, and no amount of tuning fixes distance. Pick the region closest to most of your players. If that is already true and it still feels wrong, it is worth a ticket rather than another setting.
