Seeing stutters, rubber banding, or slow block breaks? In this guide you will learn the fixes that make the biggest difference, how to size RAM, and what to try when the CPU is the limit. We will keep it simple and test one change at a time.

Start with enough RAM

RAM keeps chunks, entities, and mods ready. Use these baselines, then adjust after a short test.

• 1 to 5 players on vanilla: 2 to 3 GB
• 6 to 10 players on vanilla: 4 GB
• 11 to 20 players on vanilla: 6 GB
• Modpacks: add 2 to 4 GB

If lag remains even with spare memory, the limit might be CPU.

Close heavy background apps

Browsers, launchers, video tools, and editors can use a lot of CPU and RAM. Close what you do not need while hosting. This often removes spikes on its own.

Reduce server workload

Lower view and simulation distance. Tidy large mob farms and avoid constant hopper clocks. Do not leave thousands of items on the ground. These changes reduce work each tick.

Match versions

Make sure Java, the loader, Minecraft, and mods all match. If lag started right after a change, remove that change and test again. Small steps find the cause faster.

When CPU is the limit

If RAM is fine but ticks still drop during busy moments, lower simulation distance and reduce big redstone clocks or always-on farms.