11 min read

Optimising Server Performance

Tune your server for the best performance with JVM flags, view distance, and plugin optimisation.

By Lodgichost Team · Last updated: August 19, 2026

Server performance is the defining factor of whether players stay. Lag spikes, rubber-banding, and chunks that fail to load slowly bleed your community, while a server that holds steady at 20 TPS feels crisp even under a full player count. The good news is that most Minecraft lag is not a hardware problem — it is a configuration problem. Wrong JVM flags, view distances set too high, unlimited mob caps, and bloated plugin lists account for the vast majority of performance issues. This guide walks through the settings that matter, how to measure your server objectively, and how to apply changes without breaking what already works.

JVM Flags

JVM (Java Virtual Machine) flags control how Minecraft allocates and manages memory. Using the right flags can significantly improve server performance, especially for modded servers with large player bases.

-Xms2G -Xmx4G -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true

Apply these flags in your server startup settings in the portal. Adjust -Xmx (maximum RAM) to match your plan's allocation.

View Distance and Simulation Distance

View distance controls how far players can see chunks from their position. Lower values reduce server load. For most servers, a view distance of 6-8 chunks provides a good balance between visual quality and performance. Simulation distance controls which chunks process entities and redstone; setting it to 4-5 chunks saves significant CPU.

view-distance=6
simulation-distance=5

Plugin and Server Optimisation

Remove unused plugins to free up memory and CPU. Some plugins are notorious for causing lag even when idle.

spawn-limits:
  monsters: 50
  animals: 8
  water-animals: 5
  water-ambient: 10
  water-underground-creature: 5
  axolotls: 3
  ambient: 1

entity-activation-range:
  animals: 16
  monsters: 24
  raiders: 48
  misc: 8
  water: 8
  villagers: 16
  flying-monsters: 32

Optimise spawn limits and entity activation ranges in paper.yml or purpur.yml:

Use Lithium (Fabric) or Pufferfish (Paper fork) for automatic optimisations.
Replace heavy plugins with lightweight alternatives (e.g., use CommandPanels instead of ChestCommands).
Set a reasonable mob cap — 50 monsters and 8 animals per player is usually sufficient.
Enable entity activation ranges to reduce processing for distant entities.

Hardware Considerations

Minecraft server performance depends heavily on single-core CPU speed. Our Ryzen 9 9950X processors deliver excellent single-threaded performance. For modded servers, prioritize RAM allocation — we recommend 4 GB for light modpacks and 8+ GB for heavy packs. NVMe storage ensures fast chunk loading and world saves.

Measuring Server Performance

You cannot fix lag you cannot see. Before changing anything, measure your server with two built-in commands:

/tps
/timings report

Run them a few times at peak player counts to build a baseline, then change one setting at a time and re-measure — that way you know exactly what helped:

/tps shows ticks per second, your server's heartbeat. 20 is a perfect score, 18 and below means players will notice rubber-banding.
/timings report (Spigot/Paper) generates a breakdown of where tick time is spent, showing which plugins and chunk sections cost the most.
Watch the memory graphs in your portal during the same window to see whether your problem is CPU, RAM, or storage-bound.

Troubleshooting

High tick lag: Check your TPS (ticks per second) with /tps. Values below 18 indicate performance issues.
Memory spikes: Monitor RAM usage in the portal. Consider upgrading your plan if you regularly exceed 80% allocation.
Plugin conflicts: Temporarily disable plugins one by one to identify the culprit.

Frequently Asked Questions

What is a good TPS to aim for?

20 is perfect, and most players cannot perceive dips down to about 18. Sustained values below 18 mean visible rubber-banding and delayed block interactions. If you sit below 20, run /timings and address the largest contributors first.

Should I allocate all my RAM to Minecraft?

No — allocating more than ~12 GB rarely helps and can make garbage collection worse, since the JVM spends more time scanning a larger heap. Match -Xmx to your plan and player count, and let the OS keep some headroom.

What is the first thing I should check when players report lag?

Measure /tps, check the portal memory graph, and look for any plugin or mod pack known for server-side lag. Then work through view distance, entity limits, and JVM flags in that order — they are the biggest, cheapest wins.

Is Paper better than vanilla for performance?

Yes, for most servers. Paper is the de facto standard — it is a drop-in replacement that runs vanilla servers faster, adds /timings, and includes optimisations like per-player mob spawns. Modded servers should choose the loader their pack requires.

Does view distance matter as much on good hardware?

Single players rarely stress a fast server, but every additional chunk of view distance multiplies the work per player. Once your whole population is online, view distance and entity counts dominate CPU load — keep them sane even on strong hardware.

Related Guides

Server Properties Guide — optimise your server.properties
How to Install Modpacks — choose performance-friendly modpacks
Understanding DDoS Protection — protect your optimised server