What Actually Causes Minecraft Server Lag
Server lag in Minecraft has two distinct causes that players often confuse. The first is tick lag: the server's main thread falls behind on its 20-ticks-per-second schedule, causing the game world to advance slower than real time. Players experience this as rubber-banding, mobs that stop moving, blocks that do not respond to being broken, and actions that feel delayed. The second is network lag: the round-trip time between a player's client and the server is high, causing players to see their position jump back after moving. Tick lag is a server-side problem caused by insufficient CPU performance or too much work per tick. Network lag is a connectivity problem caused by physical distance, routing quality, or packet loss. Most complaints about "server lag" in survival Minecraft are actually tick lag, and that is entirely determined by the server's CPU performance and configuration. Network lag is separate and addressed differently.
TPS and How to Measure It
TPS stands for ticks per second, and it is the standard measurement of Minecraft server performance. A healthy server runs at exactly 20 TPS, which means the game world advances 20 times every second exactly as intended. When TPS drops below 20, everything in the game world slows down proportionally. At 10 TPS, mobs move at half speed, crops grow half as fast, and player actions take twice as long to register. You can check TPS in real time by installing the Spark profiler plugin and running `/spark tps`, or on Paper servers by using the built-in `/mspt` command that shows milliseconds per tick. A healthy server shows around 2.5 ms per tick. A server under load may show 20 to 40 ms per tick. When ms per tick consistently exceeds 50, TPS drops below 20 and players start noticing. If you want to diagnose what is causing the lag, Spark's profiler feature samples the server thread and produces a report showing which operations are taking the most time.
The Hardware Factor: Shared VPS vs Dedicated
The single biggest determinant of Minecraft server performance is the CPU it runs on, specifically single-core clock speed. Minecraft's main game loop is almost entirely single-threaded, which means a faster individual core directly improves how many operations the server can complete per tick. A shared VPS on a cloud provider might show a high clock speed on paper, but CPU resources are shared among dozens of virtual machines. When other tenants on the same physical host are under load, your VM's available CPU time decreases. This is called CPU steal, and it is invisible to most monitoring tools. A Minecraft server running on a shared VPS will have inconsistent TPS that varies based on what other customers are doing, even if your own server load is unchanged. NetSkyway runs servers on Intel i9-13900K processors at 5.8 GHz and AMD Ryzen 9 9950X processors at 5.7 GHz, both with DDR5 RAM and NVMe storage. These are consumer-grade gaming CPUs chosen specifically for their exceptional single-core performance, not server CPUs optimized for multi-tenant workloads.
Server Software Choice: Paper vs Vanilla
The server software you run has a significant impact on how efficiently it uses the available CPU. Vanilla Minecraft server is the official release from Mojang, and it is intentionally unoptimized because Mojang prioritizes correctness and compatibility over performance. Paper is a fork of the official server that applies hundreds of patches to improve tick performance, reduce unnecessary computation, and offload some work to background threads. The performance difference is measurable: on the same hardware, Paper typically runs 30 to 50 percent more work per tick than vanilla before TPS starts dropping. For almost every use case, Paper is the correct choice. The only reason to run vanilla is if you need exact vanilla parity for technical Minecraft mechanics, but even then, Paper has options to enable vanilla-compatible behavior for most edge cases. Purpur, a Paper fork, adds even more optimizations and configuration options for operators who want to fine-tune performance further.
Configuration Settings That Reduce Lag
Even on fast hardware running Paper, a few configuration tweaks make a noticeable difference. View distance is the most impactful setting: reducing it from the default 10 to 6 or 8 dramatically cuts the number of chunks the server needs to simulate simultaneously, reducing CPU load by roughly 30 to 40 percent in active play. Simulation distance (separate from view distance in newer Minecraft versions) controls how many chunks are actually ticked per server cycle; setting this lower than view distance lets players see distant terrain without the server simulating it. Entity activation range controls how many entities around each player are fully simulated versus passively tracked, and reducing it has a large effect on servers with many mobs or farms. In `paper.yml`, setting `mob-spawner-tick-rate` higher reduces how often spawner blocks are processed. None of these changes visibly degrade the player experience at normal play densities, and together they can recover several TPS on a server under moderate load.
Getting a Genuinely Low-Lag Free Server
The honest assessment is that a "no-lag free server" requires two things: hardware fast enough to handle the load, and software configured correctly to use that hardware efficiently. NetSkyway provides the hardware side with i9-13900K and Ryzen 9 9950X processors, DDR5 RAM, and NVMe storage, all on dedicated machines rather than shared cloud VMs. You provide the configuration side: use Paper instead of vanilla, set a reasonable view distance, and avoid loading the server with resource-hungry plugins you do not need. To request a server, join the Discord at discord.gg/QXKNwaWVJ2 and post in the #request-server channel. No credit card is required. Once your server is live at panel.netskyway.net, you have full access to install Paper, configure settings, and monitor TPS through the console. The hibernation system pauses the server when empty and wakes it in under a second when someone connects, keeping resources available for when gameplay is actually happening.