Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
The “Can’t keep up! Is the server overloaded?” message means Minecraft’s main server loop took longer than its 50-millisecond tick budget. A single warning can be a harmless spike; repeated warnings with low TPS or high MSPT indicate sustained lag. Measure the server first with spark, then profile slow ticks and isolate the workload or plugin responsible.
What “Can’t keep up” means
Minecraft advances the world in discrete server ticks. The target is 20 ticks per second (TPS), which gives each tick 50 milliseconds to process player packets, entity updates, mob spawning and artificial intelligence, pathfinding, redstone, chunk work, saves, and plugin tasks. Ticks run sequentially rather than in parallel. If one tick takes longer than 50 ms, the next tick cannot start on time, so the server falls behind.
As spark’s tick-loop documentation puts it, “The Minecraft server aims to run exactly 20 of these game ‘ticks’ every second, or in other words, one tick every 50 milliseconds.” When a tick finishes in less than 50 ms, the server sleeps for the remaining time before starting the next one. When it takes longer, that idle time disappears and a backlog forms.
The warning’s milliseconds and ticks-behind values describe the backlog at that instant; they do not identify the cause. The cause could be chunk generation, entities, redstone, saving, a plugin, or another task. Treat the line as an alarm to measure, not as a diagnosis.
#1 Best Overall
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
One spike versus sustained overload
- One-off spike: A teleport, first-time exploration, autosave, or scheduled task briefly exceeds 50 ms. Players may notice a short pause, but the server quickly returns to normal.
- Recurring spikes: Long ticks happen during a repeatable action, such as entering an unexplored area or triggering a farm. Average TPS can look healthy while these peaks still cause visible stutter.
- Sustained overload: The server repeatedly misses its budget, TPS falls below 20, and controls, movement, and mob behavior remain delayed. This requires reducing or relocating work rather than merely dismissing the log line.
Read the server’s actual health before changing settings
Run diagnostics during the period in which players feel lag. Changing view distance, plugin settings, or hardware before measuring can hide the bottleneck and create new gameplay problems.
Check TPS and MSPT with spark
- Join as an operator or use the console.
- Run
/spark tps. - Record current TPS, average MSPT, and the maximum or percentile values shown by the command.
- Repeat the command while reproducing the problem, then compare the readings with what players were doing.
TPS is the rate the server is achieving; MSPT (milliseconds per tick) is the time needed to process each tick. At 20 TPS, average MSPT should be 50 ms or less. A healthy average does not rule out lag: a few very long ticks can produce noticeable freezes even when most ticks are fast. Record peaks or percentile values as well as averages.
| Measurement | What it tells you | How to use it |
|---|---|---|
| TPS | Whether the server is maintaining the 20-tick-per-second target | Use during the incident; falling TPS confirms player-visible simulation delay. |
| Average MSPT | The typical time spent processing one tick | Values at or below 50 ms leave the normal tick budget; higher values indicate ongoing pressure. |
| Maximum or percentile MSPT | How severe the slowest or unusually slow ticks are | Use to catch spikes hidden by a healthy average. |
| Warning milliseconds and ticks behind | The backlog detected when a warning was emitted | Use as a timestamp for correlating the event, not as proof of a particular cause. |
Write down the context
Note the exact activity at the time of each warning: a player teleporting, exploration into new terrain, a large mob or redstone farm operating, a save, a plugin command, or a scheduled task. These observations are hypotheses. Confirm them with a profile instead of assuming that the most obvious event is responsible.
Rank #2
- Learn your way around one block at atime in the new tutorial mode
- Craft all sorts of items from boats todiamond armor and create enormousstructures
- Team up with friends in eight-playeronline multiplayer and four-player splitscreen modes
Find which ticks are slow
Use spark’s monitoring and profiling commands to move from “the server is late” to “this work made the tick late.”
Start a tick monitor
- Run
/spark tickmonitor. Spark establishes an average tick rate and monitors subsequent ticks. - Watch which ticks exceed the reported threshold. The default threshold is a 100% increase over the established average.
- If you need an absolute trigger, use a threshold such as 50 ms, the point at which a tick begins missing the normal budget.
- Leave the monitor running while reproducing the lag, then stop it after you have captured representative slow ticks.
A threshold that is too low creates noise; one that is too high can omit the first stage of a problem. Choose a value that captures the ticks players actually feel.
Profile only the long ticks
After the monitor shows a useful threshold, run a profiler with a threshold below the slow ticks you observed. For example:
Rank #3
- ENGAGING AND COOPERATIVE: Experience the thrill of Minecraft in a unique and cooperative board game format. Perfect for teams of 2 to 4 players, the game encourages joint strategies and shared victories
- EVER-CHANGING GAMEPLAY: With a map that changes every time you play, this game offers high replay value, making every game a unique and unpredictable experience
- QUALITY COMPONENTS: The game includes 25 wooden blocks, 18 world tiles, 4 inventory boards, 6 player cards, 9 buildings, 12 mob tokens and more. All components are crafted with care to enhance your gaming experience
- AGE-APPROPRIATE CHALLENGE: Aimed at ages 7 and up, this game offers a great balance of fun and challenge, making it a great choice for family game nights, parties, or gatherings
- TRUSTED BRAND: With over 130 years of experience, Ravensburger ensures top quality games that stimulate the mind, engage the hands, and touch the heart
/spark profiler --only-ticks-over 150Replace 150 with the appropriate threshold for your incident. The resulting viewer report focuses on work performed inside those long ticks. Inspect the top stack frames and correlate them with plugin code, chunk generation, entity processing, redstone, saves, or another identifiable task. A profile is more reliable than guessing from a single console line because it shows what consumed the tick time.
Use the profile to choose the right fix
Chunk generation or loading is dominant
New terrain can be expensive because the server must generate, load, and sometimes send chunks. Warnings that appear during exploration or teleportation point toward this workload, but the profile should show chunk-related frames before you act.
- Reproduce the issue with the same travel route or teleport destination so the profile captures the expensive operation.
- Review Paper’s per-player chunk-generation, chunk-load, and chunk-send limits. These controls can spread work over time instead of allowing one player’s movement to consume the whole tick budget.
- Consider the effect on exploration speed and the time required for a destination to appear. Lower limits can reduce spikes while making new terrain load more slowly.
Entities, mob AI, or pathfinding dominate
Large animal or hostile-mob populations, item piles, villagers, and complex pathfinding can consume repeated ticks. Check whether the profile’s top frames correspond to entity ticking or AI, then identify the area or farm creating the load. Remove unnecessary entities, simplify crowded mechanisms, or move high-activity builds away from the main player area. Do not apply a global reduction blindly: it can change farms and normal gameplay for every player.
Rank #4
- Minecraft Dungeons Hero Edition includes the Hero Pass DLC content: a Hero Cape, two player skins, and a chicken pet. It also includes the Jungle Awakens and Creeping Winters DLC packs.
- Dungeon Creeper Battle new-and-nasty mobs in this all-new action-adventure, inspired by classic dungeon crawlers.
- Multiplayer Up to four players can team up and fight together in co-op mode.
- Power Up Unlock dozens of unique items and weapon enchantments for devastating special attacks.
- Options Personalize your character, then fight up-close and personal with melee swings, hang back with ranged attacks, or tank your way through swarms of mobs, by heavy armor
Redstone or scheduled work dominates
Clocks, large contraptions, command systems, and recurring plugin tasks can create a steady stream of work. Compare the profile timestamp with the machine or task’s activation. Disable one system temporarily, reproduce the problem, and profile again. If the slow ticks disappear, tune or redesign that system rather than changing unrelated server settings.
Recommended Free Tools
Saves or autosaves dominate
Warnings clustered around saves indicate that persistence work is colliding with the tick budget. Confirm the timing in the profile and logs. Paper documents player-autosave limits and watchdog early-warning timing; use those controls to manage workload, but retain regular backups and verify that the resulting save behavior meets your recovery needs.
Test plugins without guessing
Plugins are a common source of long ticks, and Paper’s troubleshooting guidance recommends a controlled disable-and-test process.
Best Value
- Official Minecraft Puzzle Game – Hands-On Logic Game Based on the Best-Selling Video Game.
- 40 Strategic Challenges – Use the Actions to Navigate & Solve Increasingly Tough Puzzles.
- No Screens, Just Strategy – Promotes Problem-Solving with Off-Screen Minecraft Fun.
- Perfect for Ages 8+ – Great Gift for Minecraft Fans Who Love a Challenge!
- Trusted by Parents Worldwide – With Over 50 Million Sold, ThinkFun is the World's Leading Manufacturer of Brain Games and Mind-Challenging Puzzles!
- Stop the server and make a backup. Copy the world, configuration, and plugin files before changing anything. A backup gives you a rollback point if a configuration change damages a world or removes required data.
- Read the latest log and stack traces. If a plugin name appears in an error or slow-task trace, update that plugin from its official source and review its configuration. Updating is a testable change, not proof that the plugin was the only cause.
- Disable the complete plugin set. Rename the
pluginsdirectory or otherwise disable all plugins, restart, and reproduce the same scenario. Keep the original directory untouched so you can restore it. - Use a binary search if lag disappears. Divide the plugins into two groups, enable only one group, restart, and reproduce the issue. Keep the group that reproduces the lag; split it again. Repeat until one plugin or a small dependency chain remains.
- Keep required libraries together. A plugin may depend on a library plugin. Test dependent components as a unit so a missing library does not create a misleading failure.
- Confirm the result. Re-enable the suspected plugin alone, reproduce the same action, and capture another spark profile. The plugin is a credible cause when the slow ticks return with it and disappear without it under comparable conditions.
Restarting between each group test prevents a plugin’s in-memory state from contaminating the next result. Change one variable at a time and document which plugins were enabled for every run.
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 & 11Review Paper controls after measurement
Paper’s global configuration exposes workload controls for situations that profiling confirms are capacity or scheduling problems. The relevant categories include:
- Per-player chunk generation: Limits how much terrain generation one player can trigger.
- Chunk load and send rates: Controls how quickly chunks are loaded internally and sent to clients.
- Parallel chunk-generation workers: Selects worker-thread behavior for chunk generation. More workers are not automatically better; storage speed, CPU contention, and the rest of the server workload determine the result.
- Catchup ticks: Governs how the server attempts to catch up after a lag spike. Aggressive catch-up can make the next ticks heavier, so observe TPS and player experience after changing it.
- Player autosave limits: Shapes the amount of save work performed for players.
- Watchdog early-warning timing: Provides earlier notice of dangerous stalls, helping you capture evidence before a severe failure.
These are workload controls, not universal fixes. Before editing a configuration file, stop the server and retain a backup. Change one setting, restart, reproduce the same workload, and record TPS, average MSPT, and peak behavior. Keep a change only when it improves the measured bottleneck without unacceptable effects such as slower chunk arrival, delayed saves, or altered gameplay.
Compare server approaches using measurable criteria
Choosing between vanilla software, Paper, and a managed host should follow the workload rather than a promise that one option eliminates every warning. Use the same scenario and player count when comparing alternatives.
| Decision axis | What to measure or verify | Why it matters |
|---|---|---|
| Headroom at the target player count | TPS, average MSPT, and peak or percentile MSPT during normal play and stress events | Shows whether the server has capacity for spikes instead of merely surviving an idle test. |
| Chunk-generation and storage performance | MSPT while generating and sending new terrain; behavior during saves | Exploration and persistence can create different bottlenecks from ordinary movement. |
| Plugin or mod compatibility | Whether the required extensions run correctly and can be isolated for testing | A theoretically faster server is unsuitable if essential gameplay components fail. |
| Profiling access | Access to spark or an equivalent TPS/MSPT and tick profiler | Without measurements, you cannot distinguish a plugin problem from chunk, entity, or storage work. |
| Backups, rollback, and support | Backup frequency, restoration procedure, configuration access, and response quality | Safe troubleshooting requires a reliable way to undo changes and recover a world. |
No reviewed source establishes a universal player count per CPU, a minimum RAM amount, or guaranteed TPS for a particular host. Treat any such promise cautiously and demand measurements from a workload that resembles your own.
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 →Common fixes that do not prove the cause
- Adding RAM alone: More memory does not reduce a plugin’s computation, entity AI, redstone work, or chunk-generation time when those are the measured bottlenecks.
- Switching to an SSD alone: Faster storage can help loading and saves, but it cannot fix CPU-bound tick work or an inefficient plugin.
- Blaming the network: A network cable or faster connection cannot make the server’s simulation tick faster. Network symptoms and server-tick symptoms can coexist, so measure both separately.
- Reacting to one console line: An isolated spike may be harmless. Use frequency, player impact, TPS, MSPT, and profiles to decide whether intervention is needed.
- Disabling safeguards: Watchdogs and catch-up behavior exist to limit damage from severe stalls. Disable or loosen protections only when you understand the failure mode and have a recovery plan.
A repeatable incident checklist
- Ask players what they were doing when the warning appeared and record the time.
- Run
/spark tpsduring the incident; save TPS, average MSPT, and peak or percentile readings. - Run
/spark tickmonitorand select a threshold that captures the slow ticks without excessive noise. - Run
/spark profiler --only-ticks-over 150, or use a threshold below the slow ticks you observed. - Inspect the report for plugin, chunk, entity, redstone, save, or other dominant frames.
- Stop the server and make a complete backup before changing files or configuration.
- If plugins are implicated, update the named plugin, then use disable-all and binary-search tests while keeping dependencies together.
- If workload controls are implicated, adjust one Paper setting at a time and repeat the same test.
- Compare before-and-after TPS, MSPT, peak ticks, and player-visible behavior.
- Keep a change only when the measured bottleneck improves and backups, saves, compatibility, and gameplay remain acceptable.
The warning disappears for the right reason when the server consistently completes its ticks within the available budget under the workload your players actually generate. The objective is not to hide the message; it is to identify and reduce the work that makes a tick late.
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.
