“Minecraft server lag” can mean three different problems: the server is missing its 20-tick-per-second schedule, a player’s connection is delaying packets, or that player’s computer cannot render frames smoothly. Start with /spark tps and MSPT: if TPS is below 20 for everyone, investigate the server; if TPS stays near 20, check the affected player’s ping or frame rate instead.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
The three types of Minecraft lag
These categories are a practical troubleshooting model used by server administrators and community guides. They describe different failure points, so the first diagnostic step for one is not necessarily useful for another. A player can also experience more than one type at the same time: a busy server can have low TPS while one player is on a poor Wi-Fi connection, for example.
As an Amazon Associate I earn from qualifying purchases.
Server-side tick lag
Minecraft’s server thread advances the simulation in ticks. A healthy server aims for 20 ticks per second. When the main thread takes too long to finish a tick, the server falls behind and every player can experience delayed block updates, slow mob movement, delayed redstone and rubber-banding.
This is the problem most people mean when they ask why a Minecraft server is lagging. It is measured with TPS and MSPT, then investigated with a profiler such as spark. The important point is that the delay is in the simulation itself: the server has not completed the work needed to tell clients what should happen next.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Tick lag is normally shared. If players in different locations report that doors, combat, crops or mobs are responding late at the same time, and the server’s TPS has fallen, the main tick loop is the leading suspect. The exact cause may still be a plugin, mod, entity pile, block activity, chunk load or another task, so symptoms alone do not identify the offending feature.
Network latency
A server can maintain approximately 20 TPS while a particular player has high ping or packet loss. That player may snap backward, see delayed interactions or fail to keep up with other players, while everyone else plays normally. The server’s tick metrics will look healthy because the bottleneck is between the player’s device and the server.
Network lag affects the delivery of packets, not the server’s ability to calculate the world. A player might click a block and wait for confirmation, then see a sudden position correction when the server receives or rejects movement packets. An unstable connection can feel like freezes even when its average ping does not look extreme, so look for variation as well as a single number.
Client-side FPS lag
Client lag occurs on the player’s own computer. Low or fluctuating frames per second make camera movement and input feel choppy even when the server is running correctly. Shaders, high render distances and busy scenes commonly make this more noticeable. Other players may see the affected player moving normally because the server and network are unaffected.
FPS lag is a rendering problem. It can follow the player into single-player worlds or appear only when a particular machine renders many entities, particles or shader effects. Lowering graphics settings or disabling shaders is a useful test, but it will not repair a server whose main thread is missing ticks.
TPS and MSPT: the numbers that separate server lag from everything else
TPS (ticks per second)
TPS is the rate at which the server completes game ticks. The target is 20.0 TPS. A sustained reading well below 20 means the server cannot process the simulation on schedule. TPS is useful for confirming that a problem is server-wide, but it does not show how much spare capacity remains when the server is still hitting 20.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →For example, a server that remains at 20 TPS during a quiet period may drop as soon as players load a new region or activate a farm. Record the reading while the complaint is occurring, not after a restart or after everyone has stopped the activity. A momentary dip and a sustained 13 TPS incident require different investigations.
MSPT (milliseconds per tick)
MSPT is the time the CPU spends computing one tick. Spark’s documented target for a normal, lag-free experience is 50 milliseconds or less per tick. The arithmetic is straightforward: 1,000 milliseconds divided by 20 ticks equals a 50-ms budget. A tick taking 75 ms allows only about 13.3 ticks per second if that duration persists.
MSPT often reveals risk before TPS drops. A server reporting 20 TPS at 45 MSPT is close to its limit; one at 15 MSPT has substantially more headroom. Spark reports minimum, maximum, median and 95th-percentile MSPT, with green, amber and red indicators. Check the distribution rather than relying on one average. The median describes a typical tick; the 95th percentile shows how slow the worst regular portion of the sample is; maximum exposes the most severe individual pause.
TPS and MSPT are related but not interchangeable. TPS is an outcome over time, while MSPT is the time budget consumed by each tick. A display can round TPS to 20 while the server is repeatedly close to the 50-ms limit. Conversely, a single unusually long tick can produce a noticeable pause without moving a short TPS average very far.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Why averages miss visible lag
A server might complete most ticks in roughly 20 ms yet occasionally spend about 300 ms on one tick. The average can still look acceptable, but players will feel each long pause. Short, repeated spikes therefore require a different check from a continuously low TPS reading.
This is why a profile taken over a long period can dilute a brief event. Use the tick monitor to identify when the slow ticks occur, then capture only ticks over a threshold. Correlate the timestamp with what players were doing: a spike during chunk generation has a different lead than a spike during a scheduled plugin task.
Sleep percentage
Sleep time is the portion of a tick period during which the server has no work to do. A value under about 5 percent indicates little spare capacity and is a warning sign even if the displayed TPS remains close to 20. Treat it as a capacity indicator, not a separate kind of lag.
High sleep time does not prove that a player has a good connection or frame rate; it only says the server thread had idle time. Use it alongside TPS, MSPT and the scope of the symptoms.
Quick decision table
| What players report | Most likely cause | First check |
|---|---|---|
| TPS is well below 20 and everyone is affected | Server tick lag | MSPT, sleep percentage and a spark profile |
| TPS is about 20, but one player rubber-bands or has high ping | Network latency | That player’s ping and connection quality |
| TPS is about 20, but one player’s frame rate is low | Client FPS lag | The player’s FPS counter, render settings and shader use |
| TPS drops briefly at regular or irregular intervals | A tick spike, such as a heavy task or possible garbage-collection pause | /spark tickmonitor, followed by a thresholded profile |
The table is a triage shortcut, not a final diagnosis. If everyone has high ping at once, a host or routing problem can coexist with a healthy tick loop. If one player has low FPS during a server-wide event, that player’s rendering issue may be masking the broader tick lag. Repeat measurements under the same workload before deciding which subsystem to change.
How to diagnose server tick lag with spark
Paper bundles spark from version 1.21 onward. On other server software or older versions, first confirm that the spark commands are installed and enabled. Command names and flags can change, so use /spark help for the exact syntax supported by your build. The examples below reflect the documented forms, but a rejected option is a version-compatibility issue to resolve rather than a reason to guess at a replacement.
1. Establish a baseline
- Have players reproduce the activity that normally causes the slowdown: for example, entering a particular area, activating a farm or loading new chunks.
- Run
/spark tps. Record TPS, MSPT and sleep percentage while the problem is happening, not only after it has stopped. - Ask whether the symptoms affect everyone. A low server-wide TPS reading and widespread delay point to the main thread; a single affected player requires the network and client checks described later.
- Write down the time, location and action that preceded the slowdown. Without this context, a technically valid profile can contain plenty of normal work and very little of the work that actually caused the complaint.
2. Capture sustained lag
For a problem that lasts several minutes, start a ten-minute profile with:
/spark profiler start --timeout 600
When the capture ends, spark returns a report URL. Run it during real player activity; an empty server can hide the task that causes the lag. A ten-minute window is long enough to include recurring scheduled work, but stop and repeat the capture if the incident ends before the relevant action occurs.
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 minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall3. Catch short spikes
Use the tick monitor when the server is normally healthy but freezes for a moment:
/spark tickmonitor
The monitor’s default threshold is 100 percent above the average tick time. To flag ticks that exceed an absolute 50-ms budget, use:
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
/spark tickmonitor --threshold-tick 50
If the default is not sensitive enough for your incident, lower or raise the threshold to match the event you are trying to capture. Check the help output because flag spelling and availability are version-dependent. A threshold that is too high will miss moderate but frequent stalls; one that is too low can produce a noisy stream of harmless variations.
4. Profile only the bad ticks
After identifying a spike threshold, restrict profiling to slow ticks so normal activity does not drown out the evidence. The spark guide gives this form:
Recommended Free Tools
/spark profiler --only-ticks-over 150
Paper’s troubleshooting example starts a five-minute capture for ticks over 100 ms:
/spark profiler start --only-ticks-over 100 --timeout 300
For a shorter, less severe spike, a threshold such as 70 ms may be more useful. Use the value that matches what the monitor is actually reporting, and verify the accepted options with your server’s spark help page. A thresholded profile explains what happened in slow ticks; it is not a substitute for a normal profile when the server is consistently overloaded.
5. Read the report correctly
- Compare total time with self time. Total time includes work performed by child calls; self time is time spent in the current method itself. A large total with small self time means you should follow the expensive branch below it.
- Expand the hottest branches until you reach a recognizable plugin, mod, task or Minecraft subsystem.
- Use the Sources view to group activity by plugin or mod. This is often the fastest way to identify a suspect, but a source appearing in the report is not automatically proof that it is defective. A component may be doing legitimate work because another feature requested it.
- Match timestamps and the captured activity to the player report. A profile taken while nobody is using the farm or area that causes trouble may be technically valid but operationally irrelevant.
- Compare the 95th percentile and maximum with the median. A large gap indicates bursts or outliers that an average can conceal.
Common server-side causes and practical responses
Plugins and mods
Scheduled tasks, event handlers and poorly bounded scans can consume the main thread. The profiler’s source and call views can show which component is active during the slow ticks. Reproduce the issue with the suspected feature, then test a configuration change or temporary removal in a controlled window. Change one component at a time so you can identify the result.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Do not disable every plugin at once and then declare the problem solved: that removes the evidence and may create a different workload. First capture the incident, then test the smallest change that targets the expensive branch. If a plugin appears only in total time but not self time, inspect the child calls before blaming its code.
Ticking blocks and redstone
Large redstone clocks, constantly updating plants and other ticking blocks create work every tick. If the profile points to block ticking, locate the affected chunk or build and pause clocks, reduce update frequency or divide the workload. A farm that is harmless with one player nearby can become expensive when many copies are loaded simultaneously.
Test both the build and its surroundings. Loading several regions can multiply the number of active ticking blocks, so a single-player test may not reproduce a multiplayer incident. Compare the profile before and after pausing one clock rather than changing several farms at once.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Entities
Mob piles, item drops and other entity-heavy areas can dominate a profile through entity-ticking work. Inspect the locations that were loaded during the incident, remove unnecessary entities and prevent farms from accumulating items. Do not assume that an entity-related method alone identifies the exact build; correlate it with the area and activity in the profile.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Entity work can be intermittent: a collection system may become expensive only when a player enters the chunk, or several loaded farms may combine into a spike. Capture while those chunks are loaded and while the entity count is representative of the real incident.
World generation and chunk loading
Generating new terrain and loading many chunks can produce bursts of main-thread work. Test the same route in an already generated area to distinguish exploration-related spikes from a persistent problem. If the lag appears only while several players explore, profile during that exact scenario before changing unrelated settings.
Do not infer that every exploration freeze is a network problem merely because only traveling players notice it. Chunk generation can create server-side spikes, while the same event can also expose a weak client if the new scene is graphically demanding. TPS, MSPT and FPS separate those effects.
Garbage-collection pauses
Community guides associate periodic drops, such as a repeated fall to around 10 TPS every 30 seconds, with garbage-collection stalls and warn that using more than roughly 85 percent of allocated memory can make them more likely. Those figures are heuristics rather than a universal Java threshold. Confirm the pattern in tickmonitor and your Java or hosting metrics before changing memory settings; adding RAM blindly can hide the symptom without removing the allocation pattern that triggers it.
A regular interval is a clue, not proof. A scheduled plugin task can create an equally regular pause. Profile the slow ticks and compare them with the timing of the suspected task before attributing the event to Java garbage collection.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to tell server lag from a bad internet connection
- Check the server’s TPS and MSPT while the player is experiencing the problem.
- Ask whether other players see the same delay. If only one player rubber-bands while TPS remains near 20, investigate that player’s ping, Wi-Fi or route to the host.
- Compare behavior from a second network or location when possible. A problem that follows one connection is unlikely to be caused by the server tick loop.
- Do not use a low FPS reading as evidence of network lag. Ping measures packet delay; FPS measures local rendering.
Network symptoms include delayed interaction acknowledgements, sudden position corrections and a high or unstable ping value. They can coexist with server lag, so repeat the check during a period when server MSPT is known to be high. If every player reports similar packet delay but the tick metrics remain normal, investigate the host’s network path rather than profiling ordinary game logic.
How to tell server lag from client FPS lag
- Enable the game’s frame-rate display or another trusted FPS counter on the affected computer.
- Temporarily disable shaders and reduce render distance or other graphics-intensive settings.
- Compare the same player in a quiet area and a busy area. If frame rate changes sharply while server TPS stays near 20, the rendering workload is local.
- Ask another player watching the same scene whether they observe delayed game logic. If only one machine stutters, troubleshoot that machine rather than restarting the server.
Low FPS feels like input and camera stutter. Server tick lag changes the simulated world for many players. Those sensations can overlap, which is why measuring both frame rate and server TPS is more reliable than relying on feel. A player can have smooth FPS but still rubber-band from network delay, or high ping and low FPS simultaneously.
Free tools Windows power users keep installed
One-click scans. No signup required.
Legacy commands and what to use instead
/tps and /mspt may still work on some Paper installations, but Paper documentation treats /spark as their successor. The older timings command is deprecated. For new investigations, use spark’s TPS, tick monitor and profiler commands, then consult your server version’s built-in help if a flag is rejected.
Do not mix readings from different moments and treat them as one diagnosis. Capture the metric that corresponds to the complaint: a sustained profile for sustained lag, and a thresholded profile for spikes. Keep the server version in your incident notes because Paper and spark options can change between releases.
A repeatable incident checklist
- Write down the time, affected players and in-game activity.
- Run
/spark tpsduring the incident and record TPS, MSPT distribution and sleep percentage. - Classify the symptom as server tick, network or client FPS before changing settings.
- For sustained lag, capture
/spark profiler start --timeout 600. - For spikes, run
/spark tickmonitor, choose a threshold and capture only ticks above it. - Use Sources and call branches to identify the expensive work, then test one targeted change.
- Repeat the same workload and compare the metrics after the change.
This process prevents a common misdiagnosis: restarting a healthy server for a player’s Wi-Fi problem, or lowering graphics settings when the main thread is actually overloaded. It also leaves a record of what changed, which makes recurring incidents easier to compare instead of relying on memory.
Frequently Asked Questions
What is a good TPS for a Minecraft server?
The target is 20.0 TPS. A sustained value well below 20 means the server is missing ticks, but a displayed 20 does not guarantee plenty of capacity; check MSPT, its 95th percentile and sleep percentage too.
What is MSPT, and what number is healthy?
MSPT is the time used to calculate one server tick. Spark’s documented target for a normal, lag-free experience is 50 milliseconds or less, because 1,000 milliseconds divided by 20 ticks gives a 50-ms budget. Lower MSPT leaves more headroom.
Why does my server show 20 TPS but still lag?
The issue may be high or unstable network latency, client-side FPS lag, or short tick spikes hidden by an average. Check the affected player’s ping and FPS, then use /spark tickmonitor and the MSPT distribution rather than TPS alone.
How do I use spark to find Minecraft server lag?
Run /spark tps for a baseline. Use /spark profiler start --timeout 600 for sustained lag, or /spark tickmonitor followed by a thresholded profile such as /spark profiler start --only-ticks-over 100 --timeout 300 for spikes. Read total versus self time and inspect Sources.
What does /spark tickmonitor detect?
It watches tick duration and reports ticks slower than its threshold. Its default is 100 percent above the average; --threshold-tick 50 flags ticks over an absolute 50-ms budget. Exact flags can vary by spark and server version, so check /spark help.
Is lag caused by the server or my internet?
If TPS is near 20 and only one player rubber-bands or has high, unstable ping, the connection is the first suspect. If TPS is low and many players experience delayed simulation, investigate server tick lag. Both problems can occur together.
Is it my PC or the Minecraft server?
Enable an FPS counter. Low or stuttering FPS on one computer, especially with shaders or high render distance, points to client rendering. Server-wide delayed game logic with low TPS points to the server. Compare both measurements during the same event.
Does Paper include spark?
Paper bundles spark from version 1.21 onward. Older versions or other server software may require a separate installation or different command availability. Confirm with /spark help on the exact server build.
The Bottom Line
Measure before changing settings: TPS and MSPT identify a busy server thread, ping identifies a connection problem, and FPS identifies local rendering strain. Use spark during the real incident, profile spikes separately from sustained lag, and change one verified cause at a time.
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.
