Tencent Cloud Business KYC Benefits How to Run Minecraft Server on Tencent Cloud CVM Without Lag

Tencent Cloud / 2026-05-14 22:08:11

Before We Start: Lag Is a Feeling, Not a Fate

Lag is like that friend who always shows up late and then blames traffic on “the algorithm.” You never asked for a performance excuse; you just want your villagers to stop teleporting into the void and your creepers to stop timing your panic attacks to the exact beat of your Wi-Fi. The good news: you can run a Minecraft server on Tencent Cloud CVM in a way that’s meaningfully smoother than the typical “why is my TPS doing interpretive dance” setup.

This article is designed to be practical. We’ll go from selecting a CVM to installing the server, tuning it, opening ports, and reducing performance bottlenecks. Along the way, we’ll include troubleshooting steps that help you find where the lag is hiding: network, CPU, memory, disk, or just a too-aggressive view distance that’s bullying your server like a tiny digital tyrant.

What “Without Lag” Actually Means

Let’s define the goal so expectations don’t turn into a tragic quest. “Without lag” doesn’t mean zero latency or perfect physics. Even on a cloud server, players still experience network delay—distance, routing, and ISP behavior all matter. What we can control is server processing performance (TPS), network reliability (stable connections), and the server’s ability to respond consistently.

In other words: we want fewer stutters, fewer rubber-band effects, and a smoother tick rate. If your server maintains a stable TPS and your network path is decent, the gameplay will feel dramatically better.

Overview: The Plan in Six Steps

Choose a CVM that matches the player count and workload.
Set up networking (security groups, ports, and addressing).
Install Java and create a clean server directory.
Deploy and configure the Minecraft server (including world type and limits).
Tune performance (memory, view distance, simulation distance, entities, plugins, and garbage collection behavior).
Test and troubleshoot (TPS, logs, network checks, and rollback plans).

Step 1: Pick the Right Tencent Cloud CVM (Not the “Hope and Pray” Plan)

The biggest cause of lag is simply insufficient compute or an unhelpful machine configuration. Before we get fancy, pick a reasonable CVM. Think of the server as a tiny factory: Minecraft never stops producing work just because you turned your screen brightness down.

Estimate Based on Player Count

Rule-of-thumb guidance (because every server has different mods/plugins and hardware speeds):

1–5 players: small/medium CVM, 2–4 vCPU, 4–8 GB RAM.
5–15 players: 4 vCPU, 8–16 GB RAM.
15+ players: 8+ vCPU, 16–32+ GB RAM, plus careful plugin and world tuning.

If you run a plugin-heavy setup (economy, anti-cheat, map renderers, chat mods), bump CPU and memory accordingly. Plugins can be “small” individually but collectively behave like a buffet where everyone takes seconds.

Choose an Appropriate Region

Lag often comes from distance, not from Minecraft’s personality. Choose a Tencent Cloud region that’s geographically close to most of your players. If your players are mostly in one area, don’t place your CVM in some faraway data center unless you enjoy doing latency gymnastics.

Even within the same country/region, the network route matters. The closest region typically reduces average latency and improves consistency.

Disk Type and Storage Considerations

Minecraft performs well with decent disk performance because worlds are read/written frequently. If you can choose, opt for SSD storage. If your CVM uses network-attached storage, ensure it’s not painfully slow. During world generation or chunk saves, slow disks can contribute to stutters.

Also: keep your world data on a stable storage option. If you later migrate, make sure you don’t corrupt the region files. Corruption is the kind of lag you can’t tune away.

Step 2: Networking Setup (Where Lag Sometimes Hides in Plain Sight)

Before you install anything, make sure the network is correct. Minecraft players can’t lag if they can’t connect, but they can definitely frustrate you.

Understand Minecraft Ports

Typical defaults:

Java Edition server: TCP 25565 (unless you change it)

Tencent Cloud Business KYC Benefits If you use a different port, open that port instead. Also, if you use a reverse proxy or NAT, you may need additional configuration, but most setups just expose the server port directly.

Set Up Tencent Cloud Security Groups

You’ll need to create or edit a security group rule for your CVM. Allow inbound TCP on your Minecraft port. If you’re limiting access, restrict by IP range (for example, only your friends’ home IPs), but that’s often impractical for dynamic residential networks.

At minimum, allow inbound TCP on the server port from the internet or from the regions where players connect. Be careful: opening ports to everyone is convenient, but it also makes you visible to the world’s least patient trolls.

For safety, consider:

Changing the server port from 25565 to something else (security through obscurity isn’t real security, but it reduces noise).
Adding an IP allowlist plugin or firewall rule if you can.
Using strong server auth and good password practices for admin/operator actions.

Elastic IP or Stable Address

For consistent connections, use an Elastic IP (or otherwise stable public IP) so your server address doesn’t change. Players hate reconnecting because the IP got replaced like a surprise pop quiz.

Step 3: Install Java (Because Minecraft Isn’t a “Plug and Play” Appliance)

Tencent Cloud Business KYC Benefits Minecraft servers require Java. Newer Minecraft versions usually work best with modern Java releases. The exact version depends on your server build, but a widely compatible baseline is typically Java 17 for many modern versions.

Update System Packages

On your CVM, update package lists and core tools. The general idea is:

Update the system repositories
Install Java runtime

What commands you use depends on the Linux distribution (Ubuntu, Debian, CentOS, etc.). If you’re unsure, choose Ubuntu LTS for simplicity and broad community support.

Pick the Correct Java Version

Use the Java version recommended by the Minecraft server platform you choose (vanilla, Paper/Spigot, Forge/Fabric, etc.). Using the wrong Java can cause crashes, weird performance problems, or log messages that read like a doctor explaining you have “complications.”

Step 4: Download and Deploy the Minecraft Server

Now for the main event. You’ll create a directory, download the server JAR, and start it once to generate configuration files.

Create a Server Directory

Pick a path like:

/opt/minecraft
or /home/youruser/minecraft-server

Keep it consistent. You’ll thank yourself later when you’re hunting logs at 2 a.m. because someone spawned 400 villagers with a single click.

Choose Your Server Software: Vanilla vs Paper

Vanilla Minecraft can work, but Paper (or another performance-focused server fork) often improves server responsiveness and reduces lag spikes significantly. If your goal is “without lag,” Paper is usually the sensible choice for Java Edition communities.

If you need mod support, you may choose Forge or Fabric. Those can be excellent too, but performance tuning will depend heavily on mods.

In this guide, we’ll focus on a high-performance approach conceptually. The configuration ideas still apply even if you’re using vanilla.

First Start: Generate Files and Confirm Basics

Tencent Cloud Business KYC Benefits After downloading your server JAR, run it once. The first run creates:

eula.txt
server.properties
logs

You must accept the EULA by setting eula=true in eula.txt. Then you can start normally.

Step 5: Configure server.properties for Less Lag

Now we tune the knobs that directly influence lag: world generation behavior, player view distance, entity simulation, and some chunk-related behavior.

Recommended Baseline Settings

Open server.properties and consider the following principles:

Reduce view distance if your player count is high.
Use a reasonable simulation distance (especially on forks like Paper).
Keep spawn settings stable so the server doesn’t constantly regenerate heavy areas.
Prefer a pre-generated world over generating chunks while players roam.

Key Settings to Look At

Depending on version and server software, you’ll see settings like:

Tencent Cloud Business KYC Benefits view-distance: How many chunks are visible to players.
simulation-distance: How far the server simulates certain game logic.
max-tick-time (or equivalent): Watchdog settings.
spawn-protection: Helps protect spawn area from griefing (not performance-related, but useful).
online-mode: Should be enabled for authentication (security).

Higher view distance is a “pretty but expensive” slider. If you want smooth performance, lower it and let players keep their frames.

Step 6: Tune Memory and Garbage Collection (Yes, This Matters)

Tencent Cloud Business KYC Benefits Minecraft is Java-based, which means it uses a garbage collector (GC). If your memory and GC settings are wrong, you can get periodic pauses that appear as lag spikes. Think of GC pauses like the server taking a slow inhale and then forgetting what it was doing.

Set JVM Heap Size Carefully

You typically configure heap using environment variables or startup scripts. A common starting point might be:

Xms (initial heap) and Xmx (max heap) set to the same reasonable amount.

General guideline: allocate enough memory for world activity but leave headroom for the OS. Don’t give Minecraft so much memory that the system itself struggles to breathe.

Examples (not strict rules):

4 GB RAM server: maybe 2–3 GB heap for Minecraft.
8 GB RAM server: maybe 4–6 GB heap.
16 GB RAM server: maybe 8–10 GB heap.

Exact values depend on mods/plugins, view distance, and player count. Start moderate. If you see out-of-memory errors, increase carefully. If you see swapping or heavy OS pressure, reduce.

Use a Modern GC Strategy

Some server operators use G1GC or other modern collectors for smoother performance. The best configuration depends on your Java version and server platform. The key idea is: avoid garbage collection settings that cause frequent long pauses.

If you’re unsure, start with recommended JVM flags for your server software’s documentation. If you change too many variables at once, you won’t know what fixed the problem, what created it, and which one was the “usual suspect.”

Performance Settings: Paper/TPS Tuning That Actually Helps

If you’re using Paper or a similar optimized server, you’ll have extra configuration options that reduce lag spikes. Even if you’re not, the underlying concept is the same: reduce expensive entity behavior, control chunk updates, and avoid letting the world generate chunks in the middle of player fights.

Lower View and Simulation Distances (The “Pleasant Sacrifice”)

Start with a modest view distance like 6–10 for many public servers. Private servers can sometimes run higher view distance if player count is low and world size isn’t insane.

Try:

Tencent Cloud Business KYC Benefits view-distance: 6–10
simulation-distance: 4–8 (or similar)

Test after changes. The goal isn’t to make Minecraft look ugly; it’s to avoid turning your server into a slideshow.

Control Entity Spawns and Mob Farms

Entities are expensive. If your server has mob farms, the lag can become self-inflicted. Things like:

Too many animals
Auto-farms generating massive entities
Frequent TNT/cannon contraptions

can degrade TPS. Consider rules or plugins that limit entities, or configure spawn limits in server settings.

Also, for players: remind them that “efficiency” in Minecraft is measured in both energy and entity count. A farm that creates 10,000 items per minute is not “smart”; it’s a performance weapon.

World Generation: Pre-generate Before Players Arrive

Chunk generation is CPU heavy. If players explore a lot right after startup, your server will generate chunks while also handling players. That can cause lag spikes.

Approaches:

Use a world created ahead of time.
Pre-generate the world boundaries using a tool like a world pre-generator.
Throttle generation to avoid saturating CPU.

If you don’t want to pre-generate, at least avoid launching a huge exploration server immediately after reset. Let the server warm up.

Network Tuning: Reducing Rubber-Banding

Sometimes your server TPS is fine, but players still feel “lag” because packets arrive late or inconsistently. This can happen due to routing, bandwidth limits, or client network conditions.

Check Bandwidth and Traffic

Look at your CVM’s network metrics. Ensure you have enough bandwidth. Minecraft isn’t the world’s most bandwidth-hungry game, but multiple players with frequent chunk streaming can add up.

If you see saturation, upgrade network capacity or reduce view distance to reduce chunk streaming overhead.

Consider TCP vs UDP and General Routing Realities

Tencent Cloud Business KYC Benefits Minecraft Java uses TCP. That means packet loss can cause retransmissions and latency spikes. If your network route is unstable, players may rubber-band even if CPU is fine.

Fixes involve selecting a better region and ensuring your CVM is healthy. There’s no secret packet-hacking spell that beats bad routing.

Step 7: Use a Startup Script and Run as a Service

You want your server to start reliably after reboot. Also, you want logs. Nobody enjoys logging in manually to type “screen -r” like they’re casting a spell from a medieval Linux tome.

Use tmux or screen for Interactive Sessions

Tools like tmux help you detach and reattach to the console. If the SSH session drops, the server keeps running.

Prefer systemd for Production Reliability

Use a systemd service to start the server on boot and restart it if it crashes. This improves uptime and reduces the “server is down, what now” panic.

Make sure permissions are correct and your user has access to the server directory.

Step 8: Open the Right Ports and Verify Connectivity

After configuration, you need to verify that players can actually connect and that your security rules allow traffic.

Confirm the Server Is Listening

On the CVM, check that Minecraft is listening on the expected port. If it’s not, you’re not a lag wizard—you’re just staring at a server that never woke up.

Check Firewall Inside the CVM

In addition to Tencent Cloud security groups, your Linux firewall (if enabled) can block the port. Verify iptables/ufw settings accordingly.

Test From a Client

Try connecting from a local machine (or one of your friends). If the connection times out, it’s usually port/firewall/network related. If it connects but performance is bad, it’s usually compute or settings.

Troubleshooting: “My Server Is Laggy” Isn’t a Bug Report, It’s a Cry for Help

Let’s convert “it’s laggy” into a diagnosis workflow. Here are common symptoms and likely causes.

Symptom 1: Players Get Timed-Out or Can’t Join

Security group not opening the port.
Wrong server port in server.properties.
Firewall on CVM blocks inbound traffic.
Server is offline or crashed on startup.

Fix: verify port, confirm process is running, check logs, and ensure inbound TCP is allowed.

Symptom 2: Players Join but Movement Feels Slippery (Rubber-Banding)

Network instability or packet loss.
CPU pegged due to chunk generation or heavy farms.
GC pauses causing periodic stutters.
High view distance causing extra chunk streaming load.

Fix: check TPS, check CPU usage, check logs for GC pauses, lower view distance, and consider pre-generating chunks.

Symptom 3: TPS Drops Near Certain Areas

Large redstone contraptions running constantly.
Mob farms producing huge entity counts.
Water/lava update storms.
Player-built “physics art” that is mostly physics liabilities.

Fix: remove or throttle the heavy area, consider entity limits or redstone/automation restrictions via plugins or policies, and optimize those builds.

Symptom 4: The Server Runs Fine for 10–20 Minutes, Then Gets Worse

Memory leak or plugin behavior accumulating state.
Too much entity/item accumulation.
World corruption or extremely heavy activity over time.
GC struggling due to heap configuration.

Fix: review logs for recurring warnings, check memory usage trends, and restart gracefully if necessary while investigating root cause.

Optional: Plugins That Help Performance (Without Turning Your Server Into a Science Fair)

Plugins can improve performance, but too many plugins can cause their own overhead. Choose performance-focused tools and install only what you need.

Performance/Management Categories

Anti-lag plugins that limit entities or optimize certain behaviors.
World management tools (backups, auto-trim, chunk management).
Economy/admin plugins that don’t aggressively run tasks every tick.

If a plugin runs heavy tasks frequently, it can increase lag. Prefer plugins known for efficiency, and check configuration carefully.

Backups: Because RNG Already Exists, We Don’t Need Disaster RNG

Lag is annoying, but corrupted worlds are the kind of pain that makes you age in dog years. Backups are not optional if you care about your world.

Backup Frequency

For private servers with fewer changes: daily might be enough. For active servers: hourly or more frequent backups are safer.

Backup Method

Back up the entire world directory.
Store backups on a safe storage location (not just the same disk).
Test that you can restore from backups (yes, actually test).

A backup you can’t restore is like a parachute you found in a box labeled “For Later.”

Security Basics (So You Don’t Invite Trouble to Your Dungeon)

If your server is public, basic security matters. Some people treat Minecraft servers like an all-you-can-eat buffet. You want to lock the door and keep the snack police away.

Enable Online Mode

Use online-mode=true when possible. This helps prevent unauthorized access. If you’re running offline mode for compatibility, consider additional authentication measures or whitelisting.

Use Strong Admin Practices

Limit operator permissions.
Use secure SSH keys for access to the CVM.
Keep your server software updated.

Practical “Good Defaults” Checklist

If you want a quick checklist to reduce lag quickly, here it is:

Pick a CVM region close to players.
Use SSD storage and adequate CPU/RAM.
Use Paper (if compatible) for better tick stability.
Set view distance reasonably (don’t max it like it’s a video card benchmark).
Set simulation distance conservatively.
Tencent Cloud Business KYC Benefits Give Java a sensible heap size and avoid starving the OS.
Pre-generate world chunks for large worlds.
Open the correct TCP port in Tencent security group and Linux firewall.
Monitor CPU, memory, and TPS.
Back up your world and configs.
Review logs after changes to see if they improved anything.

A Sample Performance Workflow (So You Don’t Randomly Flick Switches)

Here’s a reliable workflow when optimizing. It keeps you from turning debugging into a circus:

Baseline: Start the server with moderate defaults. Let players test for 10–15 minutes.
Check TPS: Identify whether lag is “server-tick lag” or “network lag.”
Monitor resources: CPU and RAM usage tell you where pressure is happening.
Make one change at a time: For example, reduce view distance by 2 chunks and test again.
Repeat: Continue tuning one variable at a time.
Document: Keep a small change log so you remember what worked.

Because if you change five things and performance improves, you won’t know which lever pulled the rabbit out of the hat. And rabbits are cute, but debugging is not.

Tencent Cloud Business KYC Benefits What To Do If You Still Have Lag After Tuning

If you’ve tuned settings and the server remains laggy, it’s time to suspect deeper issues:

Oversubscribed instance: Some cloud instances can perform unevenly under load. Try a different CVM type.
Plugin inefficiency: A poorly configured plugin might run expensive tasks too frequently.
World hotspots: One area causes constant chunk updates or heavy entity behavior.
Network path issues: Players far from the region will experience higher latency no matter what you do.
Java mismatch: Confirm Java version matches server software requirements.

At this point, the best move is to read logs, identify repeated warnings/errors, and check whether the server is hitting CPU spikes or GC pauses.

Conclusion: Smooth Gameplay Is a Combination of Choices

Running a Minecraft server on Tencent Cloud CVM can be a fantastic setup when you choose the right instance, configure networking correctly, and tune Minecraft settings to match the workload. “Without lag” is achievable in the practical sense: stable TPS, fewer spikes, and better responsiveness for your players.

Remember: lag is rarely caused by one thing. It’s usually a cocktail of view distance, entity load, CPU pressure, and occasionally a network route that decides to be dramatic. The good news is that each ingredient is manageable. Tune gradually, test often, and keep backups—so your world doesn’t become a cautionary tale.

Now go forth and build. May your chunks load quickly, your farms stay efficient, and your server never mysteriously decide to “just lag for fun.”