When you run or play on a multiplayer game server, the server is constantly processing player movement, game logic, physics, AI, entities, and other changes in the game world. It needs to complete these tasks repeatedly to keep the game simulation moving.
Game server TPS, or Ticks Per Second, is a measurement used to describe how many simulation ticks a server processes each second. If a server maintains 20 TPS, it is processing 20 ticks per second under that workload.
TPS is particularly useful when you are trying to understand server performance. A server can have enough RAM and a fast internet connection but still struggle if its CPU cannot complete the required simulation work quickly enough.
In this guide, you will learn what game server TPS means, how it works, what different TPS values represent, how TPS differs from tick rate and FPS, why TPS drops, how to check it, and what you can do to improve it.
What Is Game Server TPS?
TPS stands for Ticks Per Second. It indicates how frequently a game server processes its simulation updates.
A tick is one iteration of the server’s simulation loop. During a tick, the server may process different tasks depending on the game, including player actions, movement, physics, AI, entity behavior, and changes to the game world.
For example, if a server is maintaining 20 TPS, it is processing approximately 20 simulation ticks every second.
If its workload becomes too heavy and it only manages 15 ticks per second, its actual TPS has dropped to 15.
This is why TPS is useful for diagnosing server performance. It gives you an indication of whether the server is keeping up with the workload it is expected to process.
What Does One Tick Represent?
A tick is not necessarily one complete visual frame.
Instead, it is a server side simulation update. The exact work performed during each tick depends on the game’s engine and server software.
A tick may involve:
- Processing player movement
- Updating game logic
- Running AI behavior
- Processing physics
- Updating entities
- Handling interactions
- Applying game rules
- Processing scheduled tasks
Different games divide and schedule this work differently, so you should not assume that one tick contains exactly the same operations across every game.
How Does Game Server TPS Work?
A game server continuously runs its simulation and processes updates according to its server architecture.
Imagine a server designed to maintain 20 ticks per second. The theoretical time available for each tick is approximately 50 milliseconds.
If the server can complete the required work within that time, it can maintain the intended rate.
At 60 TPS, the available interval is much smaller, approximately 16.7 milliseconds per tick.
That means a higher update frequency gives the server less time to complete each individual tick.
The important part is not simply how many ticks the server is configured to target. The server also needs enough processing capacity to complete those ticks consistently.
What Happens When a Tick Takes Too Long?
Suppose a server is targeting 20 TPS, but one tick requires significantly more processing than expected.
If individual ticks repeatedly take too long, the server may fall behind its target.
That can result in a lower measured TPS and, depending on the game, symptoms such as delayed simulation updates, slower game world processing, or inconsistent gameplay.
The exact symptoms vary between games because each game engine handles timing and synchronization differently.
What Do 20, 30 and 60 TPS Mean?
TPS tells you how many simulation updates are processed per second.
| TPS | Approx. Tick Interval | Updates Per Second |
| 20 TPS | 50 ms | 20 |
| 30 TPS | 33.3 ms | 30 |
| 60 TPS | 16.7 ms | 60 |
The higher the TPS, the more frequently the server simulation is updated.
However, you should not interpret this table as a universal performance ranking.
A game designed around 20 TPS is not automatically performing poorly because another game uses 60 TPS. Different game engines and networking architectures are designed around different simulation models.
What matters is whether the server can reliably maintain the update rate expected by that particular game.
What Is the Difference Between TPS and Tick Rate?
TPS and tick rate are closely related terms, and some games or server tools may use them interchangeably. However, there is a useful distinction when discussing server performance.
Tick rate generally refers to the frequency at which the server is intended or configured to update its simulation.
TPS refers to the number of ticks the server is actually processing per second as a performance measurement.
For example, suppose a server is configured to target 60 updates per second.
Under a light workload, it may maintain approximately 60 TPS.
If the workload becomes too heavy and the server can only process 45 ticks per second, the actual TPS has fallen even though the configured target has not changed.
So, when troubleshooting performance, the actual TPS can tell you more than the configured rate alone.
Terminology can vary by game and server software, so always check how the specific game defines and reports these values.
What Is the Difference Between TPS and FPS?
TPS and FPS measure different parts of a multiplayer gaming system.
TPS relates to the server’s simulation updates, while FPS, or Frames Per Second, describes how frequently a player’s device renders visual frames.
| TPS | FPS |
| Server side measurement | Client side measurement |
| Ticks per second | Frames per second |
| Related to game simulation | Related to visual rendering |
| Affected by server workload | Affected by client hardware and graphics settings |
| Helps assess server simulation performance | Helps assess visual smoothness |
For example, your computer might render a game at 144 FPS while the server is maintaining its normal simulation rate.
This does not mean the server is running at 144 TPS.
Likewise, a server can maintain its intended TPS while your computer produces low FPS because its GPU or CPU cannot render the game efficiently.
Network latency is another separate factor. A player can have high FPS and healthy server TPS but still experience a poor connection because of latency or packet loss.
What Causes Low Game Server TPS?
When TPS drops, the first step is to identify what is making the server work harder than it can handle.
Several factors can contribute to low TPS.
CPU Bottlenecks
The CPU performs much of the work required to run the game simulation.
If the server has too much simulation work to complete within the available time, CPU limitations can cause ticks to take longer.
This can become more noticeable as player counts, entities, AI activity, scripts, or other workloads increase.
For some games, individual core or single thread performance can also matter because not every part of a game server can scale perfectly across many CPU cores.
Too Many Players
More players usually mean more activity for the server to process.
Each player can generate movement, interactions, inventory changes, combat events, network activity, and other simulation tasks.
A server that runs smoothly with a small group may therefore struggle when the player count increases significantly.
Too Many Entities
Depending on the game, entities can include NPCs, mobs, vehicles, items, projectiles, or other interactive objects.
Large numbers of active entities can increase the amount of simulation work required during each tick.
A heavily populated area may therefore cause more performance pressure than a quiet part of the same game world.
Heavy Mods and Plugins
Mods and plugins can add valuable functionality, but some can also introduce substantial CPU or simulation overhead.
Poorly optimized code, frequent database operations, complex scripts, or inefficient event processing can increase server workload.
If TPS drops after installing a particular mod or plugin, test the server with that component disabled where practical.
Complex Server Worlds
A busy or highly developed world can create additional work for the server.
The impact depends heavily on the game engine. World size itself is not always the problem. Active entities, world simulation, AI, physics, scripts, and other dynamic systems can be more important.
Background Workloads
If your game server shares a machine with other applications or servers, those workloads can compete for CPU and memory resources.
This is especially important on VPS and dedicated servers hosting multiple services.
Insufficient Resources
Sometimes the workload simply exceeds what the server hardware can comfortably handle.
When optimization has been exhausted and the CPU remains the limiting factor, moving to stronger hardware may be the appropriate solution.
How to Check Game Server TPS
The exact method for checking TPS depends on the game and its server software.
Some games provide console commands, administrative commands, built in performance displays, or server monitoring tools.
Your hosting provider may also expose server metrics through its control panel.
When checking TPS, do not test only when the server is empty.
Monitor it during realistic workloads, especially when:
- Several players are online
- Many entities are active
- Players are exploring new areas
- Combat or other intensive events are taking place
- Mods or plugins are heavily used
Also compare TPS with other metrics such as CPU usage, RAM usage, player count, and network conditions.
This helps you identify whether the problem is actually server simulation performance or something else.
Check Average Performance, Not Just One Reading
A temporary TPS drop does not necessarily indicate a serious server problem.
For example, a short spike caused by a large event may recover quickly.
Repeated or sustained drops are more useful for diagnosing a performance bottleneck.
If your monitoring system provides historical data, look for patterns rather than relying on a single measurement.
How to Improve Game Server TPS
Improving TPS starts with finding the actual bottleneck.
Do not immediately add more RAM or move to the most expensive hosting plan without checking what is limiting the server.
Check CPU Usage
Monitor CPU usage when TPS drops.
If the server is consistently CPU bound, reducing simulation workload may help.
If the workload cannot be reduced without affecting gameplay, stronger CPU resources may eventually be necessary.
Reduce Unnecessary Server Load
Look for workloads that are not essential to your players.
Depending on the game, you may be able to reduce:
- Excessive entity counts
- Unused plugins
- Unnecessary mods
- Background services
- Excessive simulation settings
- Resource heavy scripts
Make changes gradually so you can identify which adjustment actually improves performance.
Review Mods and Plugins
If your server uses mods or plugins, review their resource usage.
Disable non-essential components temporarily and compare TPS before and after the change.
This is more reliable than assuming a particular plugin is responsible based only on its name or features.
Optimize Server Settings
Many games provide settings that control how much of the world or how many entities the server actively processes.
Review settings related to:
- Simulation distance
- Entity limits
- AI activity
- World processing
- Server side view or activity ranges
- Game specific simulation options
Do not blindly copy settings from another server. The best configuration depends on your hardware, player count, game version, and workload.
Manage Entity Counts
If excessive entities are contributing to the problem, reduce unnecessary spawns or clean up objects that no longer need to remain active.
This can be particularly useful in games where mobs, NPCs, items, or vehicles create substantial simulation work.
Upgrade Server Resources
If the server remains CPU limited after optimization, upgrading the hardware may be the practical solution.
Consider a server with:
- A faster CPU
- Strong per-core performance where relevant
- Adequate RAM
- Fast storage
- Sufficient network capacity
Do not assume that more RAM will solve a CPU bottleneck.
RAM is important when memory is actually the constraint, but increasing it does not automatically make the game simulation process ticks faster.
What Is a Good TPS for a Game Server?
There is no universal TPS value that is considered best for every game.
The correct target depends on the game’s server architecture and the simulation rate it was designed to use.
For one game, 20 TPS may represent normal operation. Another game may use a different update frequency.
The better question is:
Can your server consistently maintain the expected TPS for the game under its normal workload?
If the answer is yes, the server is likely operating as intended from a simulation-rate perspective.
If TPS repeatedly falls below the expected rate during normal gameplay, investigate the workload and identify the bottleneck.
A stable server running at its intended rate is more meaningful than simply choosing the highest TPS number possible.
FAQs
What does TPS mean in a game server?
TPS means Ticks Per Second. It measures how many server simulation ticks are processed per second. The exact meaning and reporting method can vary between games.
Is higher TPS always better?
No. A higher TPS means more frequent simulation updates, but it does not automatically mean better performance. The appropriate rate depends on the game’s server architecture and workload.
What causes game server TPS to drop?
Common causes include CPU limitations, high player counts, excessive entities, resource heavy mods or plugins, demanding server settings, background workloads, and insufficient hardware resources.
Is TPS the same as FPS?
No. TPS measures server simulation updates, while FPS measures visual frames rendered by the player’s device.
How do I check my game server TPS?
The method depends on the game. Look for built in performance commands, server console information, administrative tools, or monitoring features provided by your hosting platform.
Does CPU affect server TPS?
Yes. CPU performance can strongly affect TPS because the server must process its simulation workload within the available time for each tick.
What is a normal TPS for a game server?
There is no single normal value for every game. Use the game’s expected or configured simulation rate as your reference and check whether the server can maintain it consistently under normal workload.
Conclusion
Game server TPS, or Ticks Per Second, is a useful way to understand how well a server is keeping up with its simulation workload. It tells you how many ticks the server is processing each second, but the ideal value depends on the game.
When TPS falls repeatedly, do not assume that RAM or internet speed is automatically the problem. Check CPU usage, player activity, entities, mods, plugins, server settings, and other workloads to find the actual bottleneck.
The goal is not to chase the highest TPS number. Your priority should be a stable server that consistently maintains the update rate expected by the game while handling its normal player and simulation workload.