Why your Minecraft server lags at 8pm (and more RAM won't fix it)

You know the pattern. Your server runs fine all afternoon. Then around 8pm — right when your friends finally get online — block breaking starts to rubber-band, mobs freeze mid-step, and the world feels like it's running underwater. You open a ticket. The host tells you to upgrade to a plan with more RAM.

Here's the uncomfortable truth: for this kind of lag, RAM is almost never the problem. Let's walk through what's actually happening.

Minecraft runs on a single thread

The heart of a Minecraft server is the tick loop. Twenty times per second, the server processes everything: entity movement, redstone, crop growth, mob AI, chunk updates. That's one tick every 50 milliseconds, and — this is the key part — the main game loop runs on a single CPU thread.

That means your server's smoothness is determined almost entirely by how much time one CPU core can give you every 50 milliseconds. Not how many cores the machine has. Not how much RAM is in it. One core, 50ms, twenty times a second.

If the work of a tick takes longer than 50ms, the server can't keep up. TPS (ticks per second) drops below 20, and everything in the world visibly slows down. That's the lag you feel.

What overselling actually means

Now look at it from a budget host's side. A typical hosting node has somewhere between 8 and 32 cores. Each Minecraft server primarily needs one good core. So a node can honestly host roughly as many active servers as it has cores.

But most customers aren't online most of the time. So the temptation is obvious: sell far more servers than cores, and bet that they won't all be busy at once. In the budget tier of this industry, packing dozens of servers per core is not a scandal — it's the business model.

The bet fails every single evening, in every time zone, at the same time. Everyone's players come home and log in around the same hours. Suddenly all those servers sharing your core actually need it simultaneously. Your server gets a slice of a core instead of a core — and a tick that needs 30ms of CPU time now takes 90ms of wall-clock time, because your process keeps waiting in line.

That's why the lag shows up at 8pm and disappears at 4am. The server didn't change. Your neighbors did.

Why "buy more RAM" doesn't help

RAM is where your world, chunks, and entities live. If you genuinely run out, you get crashes or brutal garbage-collection pauses — real problems, but different symptoms.

Prime-time rubber-banding with stable memory usage is a CPU time problem. Moving from 4GB to 8GB on the same oversold node changes nothing about how much CPU time you get at peak. You'll pay more and lag the same. Upselling RAM for a CPU problem is popular for one reason: RAM is cheap to add, and CPU contention is the thing the host can't fix without selling fewer servers.

How to diagnose it yourself

You don't have to take anyone's word for this — including ours:

1. On a Paper or Purpur server, run /tps. The three numbers are TPS averages over 1, 5, and 15 minutes. 20.0 is perfect.
2. Check it at a quiet hour (early morning). Note the number.
3. Check it again at prime time with the same players and the same world.

If TPS is 19–20 in the morning and sags into the teens every evening, your hardware allocation is being shared past its capacity. No plugin tuning or RAM upgrade will fix a neighbor problem.

What actually fixes it

• A guaranteed core share. The honest version of hosting: the host commits real CPU to your server and simply doesn't sell that capacity twice. Ask your host directly: how many servers share a core at peak? Watch how they answer.
• Fewer neighbors, honestly accounted. A host that refuses to start one more server when the node is full is annoying for them and great for you.
• Sensible server software. Paper and Purpur are dramatically more efficient than vanilla at high entity counts. They help — once the underlying CPU time is actually yours.

Lag at 8pm is not a mystery and not your fault. It's arithmetic: more servers were sold than cores exist, and the bill comes due at prime time.