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 →Minecraft server lag means the server is failing to finish its tick work quickly enough—not necessarily that anyone’s computer has low FPS. Diagnose it while players are online: on Paper, capture a Spark profile, inspect any watchdog stack trace, identify whether entities, chunks, plugins, garbage collection, or a resource limit dominate the tick, then change one relevant setting and measure again.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
What “server lag” actually means
A Java server normally aims to process 20 game ticks per second. Each tick handles world simulation, entity AI, redstone and block updates, scheduled tasks, chunk work, and plugin or mod code. When a tick takes too long, the server falls behind. Players may see delayed block breaks, rubber-banding, mobs that stop and then jump, inventories that open late, or the familiar Can’t keep up! warning.
As an Amazon Associate I earn from qualifying purchases.
This is different from client-side lag. A player can have smooth frame rates while the server is late, because the simulation—not the renderer—is the bottleneck. Conversely, one player with a slow computer can have low FPS while the server’s tick rate remains healthy. Check the server’s timings and resource behavior before changing graphics settings on every client.
Paper’s watchdog warning appears when the server has taken very long—described in its troubleshooting guidance as 10 or more seconds—to finish the current tick. The warning can precede a crash, but it is not itself a diagnosis. The first lines of the watchdog stack trace often show what the main thread was doing when it stalled.
#1 Best Overall
- 【Perfectly Fit in Server Aprons】: Our black server book size is 8.15" x 5.12" x 0.59", which can hold a regular guest checkbook and is handy to be carried in a server apron pocket, won’t be too tight or too big, efficiency as a server money holder.
- 【Stay Organized All in Needs】: 9 compartments and 1 pen holder in one serving book, with a zipper pocket to store your coins, changes, and money. Multi-functional pockets to organize checkbooks, cash, ticket books, server pads, credit cards, coupons, or any other paper documents, nice waitress accessories partner for servers.
- 【Waterproof Leather Material】: The waitress book is made of premium sturdy and longevity PU leather, Eco-friendly and odorless, features excellent workmanship and tight stitching, easy to clean. Plus an elastic pen loop to be a nice waitstaff organizer to help you hold the pen that is always away from home and improve the service speed.
- 【Portable and Long-lasting】: Our server books for the waiter are lightweight to carry around, and sturdy as a guest checkbook holder, premium material makes them sturdy and longevity and won’t easily deform or press the belly when bent over.
- 【100% Satisfaction Guarantee】: We hope you love your server book wallet and place your order with confidence, all of our men’s & women’s server books are backed by a full replacement guarantee. Any questions will be answered within 24 hours.
Match the symptom to the likely class of problem
| Observed symptom | What it suggests | Best first check |
|---|---|---|
| TPS stays low while players are active | A continuous workload such as entity ticking, block entities, plugins, or a saturated CPU | Run a normal Spark profile during the slowdown and inspect the largest sections |
| TPS is usually normal but drops in bursts | Chunk generation or loading, a scheduled task, garbage collection, or a player entering a heavy area | Use a profile that records only long ticks and correlate the time with player actions |
| Players freeze, then catch up together | The main thread is blocked or ticks are completing in batches | Capture the profile while frozen; check the watchdog trace if one appears |
| Only newly explored terrain causes spikes | Chunk generation, structure placement, or storage contention | Profile during exploration and compare with a profile in an already generated area |
| The process is killed or the panel reports memory pressure | A JVM or hosting-panel memory limit, often independent of Minecraft logic | Compare the panel limit with the Java -Xmx value and review host logs |
| One player reports stutter while everyone else is fine | Client FPS, a local connection issue, or a route-specific network problem | Compare server TPS and other players’ experience before editing server settings |
Profile the server while the lag is happening
A profile taken during a quiet period can look perfectly healthy. Reproduce the problem with representative players, farms, and locations online, then start the profiler. Paper describes a profiler as measuring characteristics of a running server; Spark is bundled with Paper starting in version 1.21.
Capture a normal five-minute profile
- Have players perform the activity that normally causes the slowdown—for example, entering a busy base or exploring new terrain.
- Run
/spark profiler start --timeout 300from the server console or as an administrator in game. - When the 300-second capture ends, open the report Spark returns. If the command reports a permission or availability error, confirm that you are using Paper and that your account can run administrative commands.
- Look for the largest share of tick time. Treat that dominant workload as the next investigation target rather than changing several settings at once.
Capture only serious tick spikes
For intermittent freezes, use:
/spark profiler start --only-ticks-over 100 --timeout 300
This focuses the capture on ticks exceeding 100 milliseconds, making it easier to see what happens during a spike instead of averaging it with normal ticks. The threshold is a diagnostic filter, not a promise that every tick under 100 milliseconds is harmless; use the report alongside what players experienced.
Rank #2
- 100% Satisfaction Warranty – Our servers book for waitress organization are handcrafted with elegant stitching that lasts. We take pride in offering our customers a waitress book made to exceptional quality standards. To ensure satisfaction, every waiters checkbook is backed by a 1-YEAR WARRANTY. If you are not 100% SATISFIED for any reason we will send you a replacement. No Questions Asked
- Holds up under Pressure – When you're taking orders the last thing you need is a flimsy waiter book that keeps bending. Our 8”x5” server books for waitress organization is the only one with a premium reinforced dual inner core. Providing an unmatched sturdy reliable writing surface that will last for years
- On Another Level – Halt the endless cycle of replacing your cheap thin black server book that barely lasts a week. This serving book for waitresses can become your permanent partner. Crafted with overwhelmingly strong attention to detail, the waiter checkbook offers an unparalleled value that you won’t regret investing in
- Scribble In Style – Impression is everything. You’re making a statement when you bring out this sleek vegan leather serving book. Our serving books have no logos or images and exquisite stitching for a professional feel your colleagues will envy
- Stay Calm and Collected – Whether you have 1 table or 7, organization is key. This server checkbook has 9 versatile pockets including a durable metal zipper to keep your cash secure. Stay on top of everything with this deluxe server book organizer and bring superior service to every customer
Read the report as a decision tree
- Entity ticking: inspect mob density, item piles, villagers, animals, and other living entities in the affected area. Reducing simulation distance can lower how far living entities are updated, but it changes gameplay behavior.
- Chunk loading or generation: determine whether the problem occurs during exploration or teleportation. Generation is more expensive than simply standing in an already loaded area, and repeated generation spikes point toward pre-generation, exploration limits, or storage investigation—not immediately toward a larger view distance.
- Block entities and scheduled tasks: look for unusually busy hoppers, furnaces, redstone systems, or repeating tasks. Isolate the location or plugin responsible before removing gameplay machines.
- Plugin code: note the plugin and method names shown in the profile. Check that plugin’s documentation and release notes for the exact Minecraft and Paper version you run.
- Garbage collection: repeated pauses associated with collection indicate JVM memory pressure or allocation behavior. Check heap settings and host limits before assuming a plugin is the sole cause.
A profile identifies where time went; it does not automatically prove that the largest entry is the only cause. For example, a plugin may trigger chunk loads, so compare the call path, timing, and player actions before deciding what to disable.
Use watchdog stack traces when the server is stuck
If Paper logs a watchdog warning, copy the first lines of the stack trace before restarting. Those lines frequently reveal whether the main thread was inside entity AI, chunk generation, plugin code, a scheduled task, or a Java memory operation. A stack trace is a snapshot, so it can miss a short-lived cause; use a Spark report when the trace is ambiguous or points only to a generic server method.
Do not repeatedly increase watchdog timeouts to hide the symptom. A longer timeout may delay the crash message while players continue to experience a frozen world. The useful question is what the thread was waiting on and whether the same path appears in more than one incident.
Free tools Windows power users keep installed
One-click scans. No signup required.
Adjust view distance and simulation distance separately
These properties solve different problems. Paper documents view-distance as the server-side radius of chunk data sent to clients. simulation-distance is the radius in which living entities are updated. Both are documented with a default of 10 and a supported range of 3–32 in the cited Paper reference; verify the defaults for the exact server version you use.
| Property | What lowering it reduces | Gameplay cost | When a profile supports changing it |
|---|---|---|---|
view-distance |
Chunk data sent to clients and related loading work | Players see less of the world around them | Chunk transmission or loading is prominent, especially when many players are spread across different areas |
simulation-distance |
Living-entity updates farther from players | Mobs and farms operate at a shorter distance | Entity ticking dominates and the report shows the work is distributed over distant areas |
Change one value, then test
- Back up the server and record the current values in
server.properties. - Lower only the property that matches the measured workload. Make a modest change rather than jumping directly to the minimum.
- Restart or apply the setting using the method supported by your server setup.
- Repeat the same player activity and run the same Spark profile. Keep the change only if tick behavior improves without unacceptable visibility or farm-distance effects.
Lower distances are a reversible optimization, not a substitute for finding a runaway plugin, an enormous entity cluster, or failing hardware. If entity ticking remains dominant at a reasonable simulation distance, investigate the entities themselves.
Check plugins, mods, and server versions
Paper’s basic troubleshooting guidance points administrators to current builds and each project’s documentation. Verify all of the following against the exact Minecraft version, Paper build, and Java runtime you operate:
- Plugin or mod support for that Minecraft release
- Known performance issues, incompatibilities, and required dependencies
- Whether the issue began immediately after an update
- Whether an update is available for the plugin, Paper, or a library it depends on
Isolate a suspected plugin safely
- Make a full world and configuration backup.
- Reproduce the lag and save a Spark report showing the suspected plugin in the hot path.
- Test in a maintenance window or a staging copy. Disable only that plugin, then repeat the same scenario.
- Compare the new profile with the original. If the lag disappears, consult the plugin author’s documentation, reduce the feature causing the work, update to a compatible build, or keep the plugin disabled.
Disabling a plugin can remove commands, protections, economies, or gameplay systems, so do not make the test on an unbacked-up production world. If the plugin is not present in the profile, leave it enabled and investigate the workload that is present.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Rule out memory and hosting-panel limits
Minecraft can be configured with enough heap for Java to start while the hosting panel still imposes a lower process limit. When the panel limit is too close to -Xmx, the operating system or host can kill the process even though the server itself has not exhausted its configured heap. A kill, abrupt restart, or panel memory alert is different from an ordinary low-TPS incident.
Compare the two limits
- Find the Java startup command and record the value after
-Xmx. - Check the host panel’s memory cap and any container or service limit.
- Compare those values with the time of the failure in the panel and operating-system logs.
- If the evidence points to the cap, reduce
-Xmxby an initial 1–2 GB or raise or disable the panel limit, but only when your plan allows it and the host confirms the change.
Reducing -Xmx gives the process more headroom under a fixed panel limit but can increase garbage-collection pressure if the heap becomes too small. Raising a limit without evidence will not fix entity, chunk, or plugin work. If you cannot change the cap, provide the host with the panel alert, process command, timestamps, and Spark findings.
Best Value
- 【Perfectly Fit in Server Aprons】: Our black server book size is 8.15" x 5.12" x 0.59", which can hold a regular guest checkbook and is handy to be carried in a server apron pocket, won’t be too tight or too big, efficiency as a server money holder.
- 【Stay Organized All in Needs】: 9 compartments and 1 pen holder in one serving book, with a zipper pocket to store your coins, changes, and money. Multi-functional pockets to organize checkbooks, cash, ticket books, server pads, credit cards, coupons, or any other paper documents, nice waitress accessories partner for servers.
- 【Waterproof Leather Material】: The waitress book is made of premium sturdy PU leather, Eco-friendly and odorless, features excellent workmanship and tight stitching, easy to clean. Plus an elastic pen loop to be a nice waitstaff organizer to help you hold the pen that is always away from home and improve the service speed.
- 【Portable and Long-lasting】: Our server books for the waiter are lightweight to carry around, and sturdy as a guest checkbook holder, premium material makes them sturdy and won’t easily deform or press the belly when bent over.
- 【100% Satisfaction Guarantee】: We hope you love your server book wallet and place your order with confidence, all of our men’s & women’s server books are backed by a replacement guarantee. Any questions will be answered within 24 hours.
Decide whether hardware or storage is actually the bottleneck
Upgrade or migrate only after a profile, operating-system log, or repeatable resource metric identifies CPU, memory, storage, or network saturation. A CPU-bound entity or plugin workload may benefit from faster single-thread performance; a generation-heavy workload may expose storage latency; a memory kill requires capacity or limit changes. Moving hosts without identifying the saturated resource can preserve the same lag at a higher cost.
When comparing hosts, ask whether the plan supplies a controllable Java memory limit, enough headroom between the panel cap and -Xmx, current Paper support, and access to logs and Spark reports. Geography and network routing matter for player latency, but they do not repair a server whose main thread is missing ticks.
Server lag, client lag, or network delay?
Signs of a server tick problem
- Several players see the same delayed interactions at once.
- Mobs, redstone, and block updates pause together.
- The console reports Can’t keep up! or a watchdog warning.
- Spark shows long ticks during the incident.
Signs of a client or connection problem
- Only one player is affected while others interact normally.
- The affected player’s frame rate drops while server tick behavior remains normal.
- Symptoms vary by network route or disappear when that player changes connection.
Do not lower server distances to cure a single player’s graphics or route issue. First establish whether the server’s measured tick workload changes at the same time.
A repeatable fix workflow
- Record the incident: note the time, online players, location, activity, console warnings, and whether the process was killed.
- Reproduce it: perform the same activity with representative players online.
- Profile: run the normal Spark command for steady lag or the over-100-millisecond command for spikes.
- Read evidence: identify entities, chunks, block entities, plugins, scheduled tasks, garbage collection, or an external resource limit.
- Check versions: verify plugin and mod compatibility with the exact Minecraft and Paper builds.
- Apply one change: adjust the matching distance, isolate one plugin, correct the memory cap, or address the measured hardware limit.
- Measure again: repeat the same scenario and compare reports. Keep a change only when the improvement is reproducible and its gameplay cost is acceptable.
This process distinguishes a sustained low-TPS workload from an occasional spike and prevents a quiet period from being mistaken for a fix. It also gives a host or plugin developer actionable evidence instead of a general complaint that the server feels slow.
Bottom line
Start with measurement, not a guessed setting. On Paper, Spark and the watchdog trace can show whether the work comes from entities, chunks, plugins, garbage collection, or a limit outside Minecraft. Lower view-distance only for chunk-send pressure, lower simulation-distance only for measured entity-ticking pressure, and change memory or hosting limits only when logs support that diagnosis. Re-profile after every material change.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick 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.
