Every hosting panel plots a dashboard of curves, and almost nobody knows which to trust. The good news: you only need three numbers to understand most server problems, and one of them explains the other two.
TPS — the one that matters most
TPS is ticks per second, and 20 is perfect. Below 20, the game world slows down — mobs crawl, redstone stalls, and the server feels "laggy." TPS is your ground truth for server performance, not RAM usage.
RAM — a trap and a tell
High RAM usage is not a problem by itself; Java uses what you give it. The warning sign is memory climbing to the limit repeatedly, or swapping to disk. Watch the trend, not the percentage.
CPU — the bottleneck nobody watches
A single Minecraft world mostly runs on one thread. That means CPU speed matters more than core count, and a single busy core explains lag that "plenty of cores" cannot fix. If one core is maxed and TPS is low, you have found your problem.
A 30-second health check
- ▸TPS steady at 20? Server is healthy — look elsewhere
- ▸TPS dipping with high CPU? Reduce load or upgrade
- ▸RAM climbing forever? Restart, then check for leaks
- ▸Chunk loading slow? Move to NVMe or pre-generate
