If a Minecraft server is lagging, diagnose it while the lag is happening instead of guessing at settings. On a Java server running Paper, use Spark to profile the active tick, inspect watchdog stack traces when they appear, and then change one measured cause at a time. The expensive work is usually entity ticking, chunk loading or generation, plugins, scheduled tasks, garbage collection, or a CPU, memory, storage, or network limit outside Minecraft.
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 server tick is one cycle in which Minecraft processes world updates, entities, redstone, scheduled tasks, chunk work, and player actions. The target is 20 ticks per second (TPS), or about 50 milliseconds of work per tick. When a tick takes longer than that, the server falls behind. Players may see delayed block breaks, rubber-banding, frozen mobs, late redstone, or a world that pauses and then catches up.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →This is different from client lag. A player can have a smooth frame rate while the server has low TPS, because the bottleneck is on the machine running the world. Conversely, a player with poor Wi-Fi or low client frame rate can appear frozen to themselves while the server remains healthy. Ask other players whether they see the same delay and check server timing before changing graphics settings.
Paper’s watchdog warning is especially important: it appears when the server has been taking a very long time—documented as 10 or more seconds—to finish the current tick. That warning can precede a crash. It is a symptom of a stuck or overloaded main thread, not a diagnosis by itself.
#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.
What to do while the lag is occurring
Collect evidence during the bad period. A profile taken after everyone disconnects or after a chunk-generation burst ends can look normal and lead you toward the wrong fix.
- Ask players to reproduce the problem or remain online while you observe it. Note the time, location, number of players, and what they were doing when the delay began.
- Check the server console for “Can’t keep up” messages, watchdog output, repeated exceptions, plugin warnings, restarts, or an out-of-memory kill.
- On Paper, start a normal five-minute Spark profile with
/spark profiler start --timeout 300. - For intermittent spikes, capture only slow ticks with
/spark profiler start --only-ticks-over 100 --timeout 300. The value is a tick-time threshold in milliseconds, so this targets ticks exceeding 100 ms rather than averaging away short bursts. - Save the report and record which workload dominates before changing a setting. Repeat the same observation after each significant change.
Spark is bundled with Paper beginning with the 1.21 server line. Older Paper builds, other server implementations, and modded stacks may require a separately installed profiler or different commands; use the tooling documented for that exact build.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsHow to read a Spark report
A profiler measures characteristics of a running server, including where tick time is spent and how the garbage collector behaves. The largest section is not automatically the only problem, but it is the best starting point for the next controlled change.
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
| Dominant work in the report | Typical evidence | First test |
|---|---|---|
| Entity ticking | Large numbers of mobs, villagers, items, minecarts, or complex AI consume the main thread. | Move away from the farm or crowded area, then compare a profile. If the spike follows that area, reduce entity counts or redesign the farm rather than lowering every server setting. |
| Chunk loading or generation | Players exploring new terrain, teleporting, or using a world border fill produces bursts. | Profile during exploration. Pre-generate important terrain during a maintenance window and limit simultaneous exploration if generation is the trigger. |
| Block entities and scheduled tasks | Hoppers, furnaces, redstone clocks, maps, and other ticking block entities appear repeatedly. | Inspect the reported location and disable or redesign the specific machine. A blanket view-distance change will not remove a local redstone loop. |
| Plugin tasks | A plugin package, event handler, command, database call, or repeating task dominates samples. | Check that plugin’s documentation and release notes for the exact Minecraft and Paper version. Test with the plugin disabled on a backup or staging copy. |
| Garbage collection | Profiles show long pauses associated with allocation and collection rather than one world feature. | Check memory use, heap settings, and logs. Do not add RAM blindly; first determine whether the process is exhausting its heap or the host is enforcing a limit. |
A profile is evidence for the next experiment, not permission to change unrelated settings. If a plugin takes most of the tick, lowering simulation distance may hide the symptom while leaving the plugin’s expensive task intact.
Use watchdog stack traces as a second clue
When Paper prints a watchdog stack trace, read the first lines that describe where the main thread was stuck. They may point to entity AI, chunk generation, a plugin callback, a database operation, or garbage collection. A stack trace can identify the immediate location of a stall, but it may not capture the whole pattern; create a Spark report during a repeatable incident when possible.
Do not treat a single watchdog event as proof that the named method is permanently broken. A legitimate world-generation operation can be slow once, while a repeating plugin task can cause the same stack to recur every minute. Compare the trace with server activity, timestamps, and a profile.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC 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 & 11Steady low TPS or intermittent spikes?
| Pattern | What players notice | Likely direction | Best confirmation |
|---|---|---|---|
| Steady low TPS | Movement, redstone, and mob updates remain slow for long periods. | A continuously expensive entity population, plugin task, loaded world, or CPU limit. | A normal Spark profile while the load is sustained; compare the dominant category with the player count and loaded areas. |
| Intermittent spikes | The server is fine, then freezes briefly during teleports, exploration, saves, commands, or scheduled jobs. | Chunk generation, periodic plugin work, garbage collection, backups, or a burst of entities. | Use the slow-tick command and correlate timestamps with the event. |
| Only one player affected | One connection freezes while others continue normally. | Client frame rate, Wi-Fi, route quality, or a client-side mod rather than global TPS. | Ask other players, check their ping, and compare with server TPS and Spark activity. |
View-distance and simulation-distance are different fixes
These two properties both use chunk-radius values, but they reduce different work. Paper documents defaults of 10 and a supported range of 3–32 for each in the cited server-properties reference; verify the effective defaults for your exact server version.
| Property | What it controls | Lowering it reduces | Gameplay cost |
|---|---|---|---|
view-distance |
The server-side radius of chunk data sent to each client. | Chunk transmission and the work required to keep distant player areas available to clients. | Players see a shorter world horizon and may receive terrain later as they move. |
simulation-distance |
The radius in which living entities are updated. | Entity ticking outside the nearer active area. | Mobs, villagers, and farms farther away may stop moving or producing until a player comes close. |
Change one property at a time. If Spark shows entity ticking as the main cost, simulation distance is the more relevant test. If chunk sending or exploration is dominant, view distance is the more direct lever. Lowering both can make the server feel better while also shortening visibility and farm range, so document the old values and restore them if the profile does not improve.
Check plugins, mods, and versions
Compatibility problems can create lag without an obvious error message. Confirm that every plugin is built for the exact Minecraft and Paper version you are running, not merely for a nearby release. Read the project’s official documentation and update notes. A plugin that hooks frequently called events, performs synchronous database or web requests, or runs a large repeating scan deserves particular scrutiny.
To isolate a plugin safely:
- Make a current world and configuration backup.
- Reproduce the issue and save a Spark report.
- Disable one suspected plugin, preferably on a staging copy or during a maintenance window.
- Restart, reproduce the same workload, and profile again.
- Compare the reports before deciding whether to keep, configure, replace, or remove the plugin.
Removing a plugin can change permissions, gameplay, data formats, or protection rules. Never use a live-world deletion as your first isolation test. Modded Fabric, Forge, and hybrid servers can expose different profilers and configuration names; do not assume a Paper optimization or plugin diagnosis transfers unchanged.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Memory pressure and hosting-panel limits
Not every memory failure is caused by Minecraft’s own heap. The Java maximum heap, set with -Xmx, can be close to or above a hosting panel’s enforced container limit. The host can then kill the process even though the Java process has not reached its configured heap maximum. Logs may show an out-of-memory kill or the panel may report memory pressure.
When that evidence is present, compare the panel limit with -Xmx and the rest of the process’s overhead. The documented responses are to reduce -Xmx by an initial 1–2 GB or raise or disable the panel limit where your host permits it. Apply the change only when the memory diagnosis fits; giving a CPU-bound server less heap will not improve TPS, and raising a limit cannot fix a plugin that blocks the main thread. If the panel limit cannot be changed or its accounting is unclear, ask the host for the container’s actual cap and kill reason.
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.
Storage, CPU, and network: prove the bottleneck first
World generation and saving can expose slow storage, while entity and plugin workloads are generally limited by main-thread CPU time. A saturated network link affects chunk delivery and player connections but does not by itself explain globally low TPS. Use repeatable metrics from the operating system or hosting panel—CPU saturation, memory pressure, disk latency, network loss—and compare their timestamps with Spark reports.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Upgrade hardware or migrate hosts only after a profile or resource metric identifies the limiting resource. A faster disk will not repair an inefficient repeating task, and more RAM will not make a single overloaded CPU core finish a tick sooner. If the same workload remains above the tick budget after plugin and world changes, a host with adequate dedicated CPU, memory headroom, and storage may be the appropriate final remedy.
A safe change-and-measure loop
- Write down the current Paper version, Java version, player count, distance settings, heap flags, and installed plugins or mods.
- Capture a Spark profile during the incident and save the console output.
- Choose one change that targets the dominant measured category: an entity reduction, a plugin configuration, a distance property, a chunk-generation plan, or a memory-limit correction.
- Restart only when the change requires it, then reproduce the same activity for a comparable period.
- Run the same Spark command again and compare slow-tick frequency, dominant stacks, TPS, and player reports.
- Keep the change only if it improves the measured symptom without unacceptable gameplay loss. Otherwise revert it and test the next hypothesis.
This loop prevents a quiet period from being mistaken for a fix. It also leaves you with a record of which setting changed, what it cost players, and whether the improvement was real.
Prevention once the server is healthy
- Keep Paper, Java, plugins, and mods on versions that their maintainers support together; read release notes before upgrading a live world.
- Profile during normal peak activity occasionally, not only after a crash.
- Pre-generate high-traffic terrain if profiles show exploration-driven generation spikes.
- Set practical limits on mob farms, item buildup, hoppers, and repeating redstone clocks.
- Keep free memory headroom under the host’s panel limit and monitor for process kills.
- Record distance settings and heap flags so a future change can be reversed quickly.
Scope: Paper versus other server types
The commands and property definitions above are strongest for Java servers using Paper, including Paper’s Spark integration from 1.21 onward. Vanilla, Fabric, Forge, and heavily modded servers can use different settings, profilers, and performance characteristics. The general method still applies—observe the lag, capture a profile or trace with the tool supported by that server, identify the dominant workload, change one cause, and measure again—but use that platform’s official documentation for command syntax and compatibility.
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.
