In brief
More RAM rarely fixes a lagging Minecraft server. The game’s main thread relies on a single processor core, so TPS, MSPT and a profiler such as spark reveal the real cause far better. We show seven common causes, how server lag differs from client lag, and safe first steps.
Measure first: what are TPS and MSPT?
A Minecraft server runs 20 ticks per second (TPS), which leaves at most 50 milliseconds per tick. If the calculation takes longer, the server falls behind and players see blocks snapping back, stuttering mobs and delayed interactions.
MSPT (milliseconds per tick) shows how long a tick really takes. 20 TPS says nothing about headroom; a 45 ms MSPT is still fine but leaves almost no margin. On Paper-based servers the /tps and /mspt commands give a quick picture.
| Metric | Healthy | Suspicious |
|---|---|---|
| TPS | Around 20, stable | Consistently below 19 or fluctuating |
| MSPT | Well below 50 ms | Peaks above 50 ms |
| Ping (client) | Appropriate for distance and network | Sudden jumps while TPS is fine |
Server lag or client lag: how to tell them apart
Everyone means something different by “lag”. Use this to separate the two cases before changing anything.
- Blocks snap back, mobs stutter, the day cycle slows: the server’s ticks are late, so the cause is on the server side.
- Low frame rate while the server is fast: a client-side cause (graphics, mods, render distance on the player’s machine).
- High ping while TPS is good: a network cause, distance or the player’s connection.
The 7 most common causes
Ordered by how often they appear, each with its typical symptom.
- 1. The single-thread limit. The main tick thread effectively runs on one core, so single-core performance matters more than core count.
- 2. Too many entities. Mob farms, dropped items and animals in large numbers slow the ticks, especially in one area.
- 3. Chunk generation. Exploring new terrain causes load spikes from world generation, multiplied when many players spread out.
- 4. View and simulation distance set too high. Every player forces that many chunks to be loaded and simulated.
- 5. A misbehaving plugin or mod. A single faulty add-on can consume a large part of the tick.
- 6. Garbage-collection (GC) pauses. An oversized memory allocation can cause longer pauses, while one that is too small causes frequent collection.
- 7. A slow disk. During saves or chunk loading, slow storage can cause repeated freezes of a few seconds.
Profiling: where the real cause shows up
Instead of guessing, run a profiler exactly while the slowdown happens. spark is a widely used option and the Paper documentation refers to it. The result shows which plugin, part of the world or process takes the most time.
Important: change one thing at a time and measure again. That is how you know what helped.
Why more RAM is not an automatic fix
Memory helps when the server genuinely runs out of it, for example with a large modpack or many loaded chunks. If the tick thread is waiting for the processor, more RAM speeds up nothing and can even bring longer GC pauses.
Choose a plan that matches the measured load and, when ordering, describe the server type, plugins or modpack so that the size fits the real need.
Minecraft server hosting with Montavio
Choose a plan that fits your community and mods; the limits are shown in numbers.
See Minecraft plans
