Minecraft server performance can be affected by CPU workload, world generation, entities, plugins, mods, player activity, view distance, simulation distance, and the amount of memory available to the server.

This guide explains common ways to diagnose and improve performance on a Down Side Hosting Minecraft Java server.

Server-side performance problems may cause:

• Blocks taking a moment to break or place
• Mobs freezing or moving slowly
• Delayed inventory actions
• Commands responding slowly
• Players being moved backward
• Redstone running slowly
• Chunks loading slowly
• Server console warnings
• Low server TPS

Not every type of lag is caused by the Minecraft server itself.

A player's internet connection or computer can also cause problems that appear similar to server lag.

Minecraft servers normally attempt to run at:

20 TPS

TPS means:

Ticks Per Second

At 20 TPS, the server is processing game activity at its intended rate.

If the server consistently falls below 20 TPS, players may notice delayed or slowed gameplay.

You may see a console message similar to:

Can't keep up! Is the server overloaded?

This means the server took longer than expected to process game ticks.

An occasional warning during startup or heavy world generation does not automatically mean the server has a serious problem.

Repeated warnings during normal gameplay should be investigated.

Giving a server enough memory is important, but adding RAM does not automatically increase Minecraft TPS.

Performance can also depend heavily on:

• CPU workload
• Plugins
• Mods
• World generation
• Entity counts
• Redstone
• Chunk loading
• Simulation distance
• Server configuration

See:

How Much RAM Does a Minecraft Java Server Need?

The amount of RAM available to your Minecraft server is determined by the hosting plan you purchased.

Customers do not manually change the server's RAM allocation through Java memory arguments.

If your workload requires more RAM, you can upgrade to a configuration with additional memory.

Before upgrading, check whether memory is actually the limiting factor.

Java startup arguments are managed by Down Side Hosting.

If a modpack, server software project, or other application specifically requires different Java arguments, contact Down Side Hosting support.

Do not assume changing Java arguments is the correct solution for every performance problem.

See:

Minecraft Java Arguments and RAM Settings on Down Side Hosting

Before changing server settings, open the Console section of your Down Side Hosting server panel.

Look for:

ERROR
WARN
Exception
Can't keep up
OutOfMemoryError

Also look for messages mentioning specific plugins or mods.

A performance issue caused by a broken plugin should be fixed differently from a server that simply has too many entities loaded.

If the server has been running for a long time, a restart can sometimes clear temporary problems.

A restart can:

• Clear inactive processes
• Reload plugins
• Reload mods
• Restart Java
• Clear temporary accumulated state

However, regularly restarting a server does not fix an underlying plugin, mod, configuration, or resource problem.

Minecraft's:

view-distance=

setting affects how much of the world is sent to players.

For example:

view-distance=10

Increasing view distance can increase server workload.

A high value may result in more:

• Chunk loading
• World generation
• Network traffic
• Memory usage
• CPU workload

If the server is struggling, lowering view distance can be one useful test.

Minecraft also has:

simulation-distance=

This determines how far around players many game systems continue to actively simulate.

This can affect:

• Mobs
• Redstone
• Farms
• Entity processing
• Other ticking game mechanics

Lowering simulation distance can reduce server workload.

However, it also changes gameplay behavior, so do not lower it more than necessary.

For more configuration information, see:

Minecraft server.properties Configuration Guide

Generating new Minecraft terrain can be CPU intensive.

Performance problems may be more noticeable when several players are exploring new areas at the same time.

World generation becomes even heavier when using mods that add:

• New biomes
• Structures
• Ores
• Dimensions
• Complex terrain generation

If lag occurs mainly while players explore new territory, world generation may be contributing to the problem.

Some server owners choose to pregenerate portions of their world before opening the server to many players.

This can reduce the amount of new terrain that needs to be generated while players are actively exploring.

Pregeneration itself can create a heavy temporary workload.

If you use a world-pregeneration plugin or mod:

• Create a backup first.
• Follow its documentation.
• Avoid extremely large generation areas unless necessary.
• Monitor server performance while it runs.

Large numbers of entities can increase server workload.

Examples include:

• Animals
• Monsters
• Villagers
• Armor stands
• Dropped items
• Minecarts
• Boats
• Projectiles

Large farms or crowded areas can therefore cause localized performance problems.

Large villager trading halls can create significant processing workload.

This can become more noticeable when many villagers are:

• Searching for workstations
• Pathfinding
• Interacting with beds
• Processing AI
• Updating trades

If lag is concentrated near a large villager area, investigate that location.

Thousands of dropped items can create unnecessary server workload.

Common causes include:

• Large farms
• Broken storage systems
• Mass block destruction
• Uncollected mob drops

Fix the source of excessive item creation rather than relying only on repeatedly clearing entities.

Large or constantly active redstone systems can affect server performance.

Examples include:

• Redstone clocks
• Large sorting systems
• Automatic farms
• Hopper networks
• Pistons
• Constantly active machines

If server performance becomes poor only when a specific farm is running, that farm should be investigated.

Large numbers of active hoppers can create additional processing work.

For very large storage systems, consider whether every hopper needs to remain active continuously.

Plugin or server-software optimization options may also exist, depending on your configuration.

Plugins, mods, or Minecraft mechanics that keep chunks permanently loaded can increase server workload even when no players are nearby.

Check for:

• Plugin chunk loaders
• Modded chunk loaders
• Forced chunks
• Large automation systems

Only keep chunks loaded when they actually need to remain active.

A plugin can load successfully and still use excessive server resources.

Potential causes include:

• Frequent database operations
• Constant world scanning
• Large scheduled tasks
• Excessive entity processing
• Poorly optimized code
• Plugin conflicts

If performance problems began after installing or updating a plugin, investigate that plugin first.

See:

Minecraft Plugin Troubleshooting Guide

If performance was good before adding a new plugin:

1. Make a backup.
2. Stop the server.
3. Temporarily remove the new plugin JAR.
4. Start the server.
5. Test performance again.

If the problem disappears, investigate that plugin's configuration, version, and compatibility.

Modded Minecraft servers can have very different workloads from Vanilla or Paper servers.

Mods may add:

• Machines
• Automation
• Dimensions
• Entities
• World generation
• Complex block behavior
• Large processing networks

A server with a modest player count can still have a heavy workload if the modpack contains complex automation.

When troubleshooting a modpack, check whether the problem is:

• Pack-wide
• Limited to one dimension
• Caused by one player area
• Caused by a specific machine
• Caused by world generation
• Introduced after an update

See:

Minecraft Mod and Modpack Troubleshooting Guide

Paper, Purpur, and Spigot provide different performance and configuration options.

For many new plugin servers, Paper is a strong starting point.

Purpur builds on Paper and adds additional configuration options.

See:

Paper vs Purpur vs Spigot: Which Minecraft Server Should You Use?

Minecraft optimization guides often contain large configuration files or dozens of recommended values.

Do not copy settings blindly.

A setting that works well for one server may negatively affect:

• Mob spawning
• Redstone
• Farms
• Villagers
• Gameplay mechanics
• Plugin compatibility

Change a small number of settings at a time and test the result.

When troubleshooting performance:

1. Identify the problem.
2. Record when it happens.
3. Make one or a few related changes.
4. Restart the server.
5. Test again.
6. Compare the results.

Changing 20 settings simultaneously makes it difficult to determine which change actually helped.

Ask whether the performance problem occurs:

• Everywhere on the server
• Near one player
• In one world
• In one dimension
• Near one large farm
• Only while exploring
• Only when a specific plugin feature runs

Localized lag often points toward a world, entity, machine, or plugin issue rather than a server-wide resource problem.

A player with a poor internet connection may experience:

• Delayed movement
• Disconnects
• High latency
• Rubber-banding

without the entire Minecraft server having low TPS.

If only one player has the problem while everyone else is playing normally, investigate that player's connection as well.

Server performance and client FPS are also different.

Low client FPS may be caused by:

• Graphics settings
• Shaders
• Resource packs
• Client mods
• GPU performance
• Large builds
• Large numbers of visible entities

Increasing server RAM will not fix low FPS on a player's computer.

High memory usage does not automatically mean the server needs more memory.

Java can retain allocated memory for later use.

Look for actual symptoms such as:

• Out-of-memory errors
• Server crashes
• Constant severe garbage collection
• Memory pressure during startup
• Modpack requirements exceeding the current plan

If the workload genuinely requires additional RAM, your Down Side Hosting plan can be upgraded.

If the console contains:

OutOfMemoryError

the server may not have enough memory for the current workload, or another problem may be consuming excessive memory.

Check:

• Current RAM allocation
• Modpack recommendations
• Recently added plugins or mods
• Player count
• World activity
• Whether memory usage continually increases

See:

How Much RAM Does a Minecraft Java Server Need?

If the server is crashing, performance optimization may not be the first problem to solve.

Check the error log or crash report.

For plugin servers:

Minecraft Plugin Troubleshooting Guide

For modded servers:

Minecraft Mod and Modpack Troubleshooting Guide

Before making major configuration changes:

• Create a backup.
• Record the original settings.
• Change only what you intend to test.
• Restart and verify the server.

See:

How to Back Up and Restore a Down Side Hosting Minecraft Server

Not necessarily.

More RAM helps when the server does not have enough memory for its workload.

It does not automatically fix CPU-heavy plugins, excessive entities, large farms, world generation, or inefficient mods.

Yes.

Your RAM allocation is based on the Down Side Hosting plan you purchased.

If your server requires more memory, you can upgrade to additional RAM.

Java arguments are managed by Down Side Hosting.

If you have a specific requirement for different Java arguments, contact support and include the reason for the requested change.

Minecraft normally targets:

20 TPS

Consistently lower TPS can indicate that the server is unable to process its workload quickly enough.

If chunk loading or world activity is contributing to performance problems, reducing view distance can reduce workload.

The ideal setting depends on your server.

Generating new chunks requires additional processing.

This can be particularly demanding on heavily modded worlds or when many players explore in different directions simultaneously.

The area may contain a large number of:

• Entities
• Villagers
• Hoppers
• Redstone
• Farms
• Machines
• Loaded chunks

Investigate the affected area rather than assuming the entire server needs more resources.

• How Much RAM Does a Minecraft Java Server Need?
• Minecraft Java Arguments and RAM Settings
• Minecraft server.properties Configuration Guide
• Minecraft Plugin Troubleshooting Guide
• Minecraft Mod and Modpack Troubleshooting Guide
• How to Back Up and Restore a Minecraft Server

When contacting Down Side Hosting support about performance, provide:

• Minecraft version
• Server software or mod loader
• Modpack name and version, if applicable
• When the lag occurs
• Whether all players experience it
• Relevant console warnings or errors
• Recent plugins, mods, or configuration changes

Contact Down Side Hosting Support

Down Side Hosting provides Minecraft Java hosting with server panel access, file management, console controls, backups, and support.

If your existing plan does not provide enough RAM for your workload, additional memory can be purchased by upgrading your server configuration.

Minecraft Java hosting starts at $2/month.

View Minecraft Java Server Hosting

← Back to Minecraft Java Server Guides