Server lag is not mysterious. It has a small number of specific causes, and they show up in a predictable order. Work through this list top to bottom and most servers land back at a stable 20 TPS without spending a cent more on hardware.
First, know which lag you have
Two different problems get called "lag" and they have opposite fixes:
- Low TPS — the server itself cannot keep up. Blocks break slowly, mobs stutter, everyone suffers equally. This is what the rest of this guide fixes.
- High ping — the server is fine, the network between you and it is not. Only some players are affected. Look at where the server is hosted relative to your players.
Run /tps on Paper to see which one you are dealing with before changing anything.
The settings with the most impact
- view-distance: drop it to 6-8 in
server.properties. This is the single biggest lever there is, and players rarely notice the difference. - simulation-distance: 5-6 is enough. It controls how far out the world stays "alive" — crops growing, mobs thinking.
- Switch to Paper if you are on vanilla or Spigot. Its config files let you cap entity counts, spawn rates and tick behaviour with real precision.
- Pregenerate the world with Chunky. Generating terrain while people play is the most expensive thing your server ever does — step-by-step guide.
Then find the real culprit with Spark
If lag survives the settings above, stop guessing. Install Spark and run /spark profiler while the server is lagging. The report names the exact plugin, chunk or farm eating your tick. Ten minutes with a profile beats a week of changing settings at random.
Entities and farms
On any survival server more than a few months old, this is the classic answer. Giant mob farms, thousands of dropped items and hundreds of hoppers all tick constantly. Cap entity stacks in Paper's config or add a per-chunk limit plugin, and clear item drops on a timer.
Plugins and mods
Plugin count matters far less than plugin quality. One badly written plugin doing database work on the main thread will out-lag thirty well-behaved ones. If Spark points at a plugin, look for a maintained alternative before you look at hardware.
When it really is the machine
If everything above is done and the server still asks for more, then it is time to move up. Because Minecraft leans so hard on one core, what you want is a host that picks nodes for per-core performance rather than advertising raw RAM. At TaroHosting each server is placed on the least-loaded Ryzen node for exactly that reason, and support will look at your Spark report with you before you spend anything.