The best Minecraft server settings for low latency depend on what kind of lag players are seeing. High network round-trip time is about the connection between a player and the server; slow or delayed game updates can mean the server is missing its tick target. Lowering server workload may improve tick performance, but it cannot shorten a network route. For Java servers running Paper, tune view-distance and simulation-distance against gameplay needs, measure performance during real activity, and treat packet compression as a CPU-versus-bandwidth tradeoff—not a ping fix.
First identify what “lag” means
There are two different problems commonly called lag:
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Supermicro MBD-X13SCL-IF-O Intel LGA-1700 Single Socket Mini-ITX Server Motherboard | $354.95 | Buy on Amazon |
- High network round-trip time: packets take a long time to travel between a player and the server and back. Server settings cannot make that physical or network route shorter.
- Server tick delay: the server takes too long to process game updates, so the world appears to update late or unevenly. Reducing server workload may help, but first measure it while the symptom is happening.
Paper’s command documentation describes 20 ticks per second as the target and says each tick needs to complete within 50 milliseconds to sustain it. Tick timing and profiling can reveal server-side workload; they do not establish the quality of a particular player’s network route. Paper’s command reference explains the tick context.
Which Paper settings affect server workload?
These settings are for Minecraft Java servers using Paper. Paper’s live server.properties reference documents the controls below. Defaults and ranges can change, so check the reference for the server version you actually run.
#1 Best Overall
- Intel Xeon 6300-series/E-2400 Series Processor, Pentium Processor, Single Socket LGA-1700 (Socket
- Intel C262 controller for 6 SATA3 (6 Gbps) ports ; RAID 0,1,5,10
- Up to 64GB ECC Unbuffered DIMM, DDR5-4800MHz, in 2 DIMM slots
- 1 PCIe 5.0 x16
- 2 SlimSAS (2 PCIe 4.0x4 or 1 PCIe 4.0x4 & 4 SATA)
| Setting | What it controls | Documented value | Tradeoff when adjusted |
|---|---|---|---|
view-distance |
How much world data the server sends to each client, measured in chunks in each direction. | Default: 10; allowed range: 3–32, according to Paper’s live reference. | Lowering it can reduce chunk-sending work and data, but players receive world data from a shorter distance. |
simulation-distance |
The radius in which entities may be located to receive server updates. | Default: 10, according to Paper’s live reference. | Lowering it reduces the area being simulated, but can change mob, farm, and other gameplay behavior farther from players. |
network-compression-threshold |
The packet-size threshold at or above which packets are compressed. | Default: 256; a negative value disables compression, according to Paper’s live reference. | Compression uses CPU while reducing transmitted data. Disabling it may save compression work but increase bandwidth use; the balance depends on available CPU and bandwidth. |
How to tune view and simulation distance
There is no evidence-based universal “best” number for every host. The right values depend on server version and software, player count, world activity, plugins or mods, available compute, and the gameplay experience you want.
- Record the current values for
view-distanceandsimulation-distancein the server’sserver.propertiesfile. - Change one setting at a time, then restart or reload the server as required by your setup.
- Test with representative players and activity—such as exploration, combat, and farms—rather than judging a quiet server.
- Check tick performance during the test and note whether the setting change improves it without making world visibility or simulation unacceptable.
- Keep or revert the change based on those results, then test the other setting separately.
view-distance governs world data sent to clients; simulation-distance governs where entities receive updates. They are related to performance but do different jobs, so changing one does not substitute for tuning the other.
Does changing network-compression-threshold reduce ping?
Paper documents the threshold as a packet-compression control, not a ping control. Setting it to a negative value disables compression. That may reduce CPU work in some circumstances, but it can increase transmitted data; keeping or lowering the threshold may use more CPU while reducing the amount sent. Paper’s reference does not promise that disabling compression lowers player ping. Change this setting only as a measured response to a CPU or bandwidth constraint, not as a general latency fix.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Profile during the lag, not after it
Paper prefers spark for profiling, and its documentation says Paper bundles spark starting with version 1.21. The same documentation describes Timings as unmaintained and deprecated. For an intermittent problem, capture data during a representative busy period: an idle profile may not show the work causing the delay.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →- When the issue is active, run
/spark profiler start --timeout 600in the server console or with the necessary in-game permissions. Paper lists this as a 10-minute profiling example. - Let the profile run through the lag rather than waiting until the server is quiet.
- Use the resulting profile to investigate server-side work, such as entities or plugins, alongside tick timing.
- If tick performance is healthy but one or more players still experience high round-trip time, investigate their connections and the network path to the server separately.
See Paper’s profiling documentation for current guidance and version-specific details.
Compare hosting under realistic conditions
A 2021 Meterstick study examined Minecraft, Forge, and PaperMC in cloud and self-hosted environments. In the deployments it tested, performance varied with workloads and environment; its reported peak response time reached 20.7 times the arithmetic mean and exceeded 7.4 times the study’s stated playability threshold. Those results describe that study’s experiments, not current hosting services or a guarantee about any provider. They are a reason to look for spikes under realistic activity, not a basis for ranking hosts. Read the Meterstick technical report.
When comparing hosts, keep the workload as consistent as possible: use the same game version, server software, world, plugins, player count, and activity. Compare network performance for the actual player group, consistency of the compute allocation, profiling support, and how easily you can change configuration. No particular provider or region is established as best by the available evidence.
Bedrock settings are different
Do not copy Paper’s Java values into Bedrock Dedicated Server. Microsoft’s Bedrock Dedicated Server properties list a view-distance default of 32 chunks and a tick-distance default of 4; the documentation warns that higher values affect performance. Microsoft’s Bedrock distance guide explains that simulation distance affects both client and server performance more than render distance, and that client and server limits interact. These are Bedrock-specific descriptions and defaults, not Java/Paper recommendations.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
