How to Optimize Your Dedicated Server for Minecraft Modpacks: RAM Allocation and JVM Arguments

Flag explanations:

• -Xms / -Xmx: Set the initial and maximum heap to the same value. This prevents the JVM from resizing the heap at runtime, which triggers full GC events.
• G1GC with MaxGCPauseMillis=100: G1 is the best GC for heaps between 4-16 GB. The 100 ms target keeps GC pauses under the 50 ms tick window most of the time.
• G1NewSizePercent=30: Allocates 30% of the heap to new (young) objects. Modded servers create many short-lived objects — this reduces promotion pressure.
• AlwaysPreTouch: Forces the OS to commit physical RAM to the heap at startup, preventing runtime page faults that cause lag spikes.
• UseLargePages: Reduces TLB misses for the heap. Requires HugeTLB or transparent hugepages enabled at the OS level.
• DisableExplicitGC: Prevents mods from triggering System.gc(), which causes full stop-the-world pauses.

CPU and Tick Rate Optimization

Modded Minecraft runs its main tick loop on a single thread. If that thread hits 100% utilization, TPS drops below 20 regardless of other resources. Key optimizations:

• CPU pinning: Use taskset to pin the Minecraft process to a single physical core. Reserve a separate core for OS interrupts and the garbage collector. On a 16-core EPYC, pin Minecraft to cores 0-3 (4 threads) and leave cores 4+ for the OS and other services.
• View distance control: Set view-distance=8 in server.properties as a starting point. Each chunk of view distance adds roughly 2-3 ms of tick time on a 50-player modded server. At view-distance=10 with heavy mods, the tick time can exceed 50 ms, causing visible lag.
• Entity and tile entity limits: Use datapacks or server-side mods to cap mobs per chunk (e.g., 20 mobs per chunk) and tile entities per loaded area. Branch mining caves with 200+ entities in one chunk is a common TPS killer.
• Simulation distance: Set simulation-distance=6 or lower. This controls how many chunks around each player actually process entities and redstone, and it is the single biggest lever for TPS improvement on any modded server.

Monitoring and Diagnostics

You cannot optimize what you cannot measure. Install at least one of these tools on your dedicated server:

• Spark: The gold standard for Minecraft server profiling. Run /spark profiler for 30 seconds to see exactly which methods consume tick time. Plugin tick handlers and entity AI are the most common culprits.
• Observable: A visual profiling tool that graphs heap usage, GC pauses, and TPS on a timeline. Useful for identifying the exact moment a lag spike correlates with a GC event.
• htop / btop: OS-level monitoring. Watch for runaway memory usage or CPU core stealing from other processes on shared hardware.

Run a baseline profile on an empty server (no players) and again with 10, 20, and 50 players. The difference shows you where your bottleneck shifts from CPU to memory to GC. If TPS drops below 18 at 30 players with 8 GB allocated, the issue is rarely "not enough RAM" — it is almost always a mod or entity group that is consuming disproportionate tick time.

Putting It All Together: A Sample Server Command

#!/bin/bash
# Modded Minecraft server launcher for 32 GB dedicated server
java -Xms8G -Xmx8G   -XX:+UseG1GC -XX:+ParallelRefProcEnabled   -XX:MaxGCPauseMillis=100 -XX:+UnlockExperimentalVMOptions   -XX:G1HeapRegionSize=4M -XX:G1NewSizePercent=30   -XX:G1ReservePercent=20 -XX:SurvivorRatio=32   -XX:MaxTenuringThreshold=1   -XX:+PerfDisableSharedMem -XX:+DisableExplicitGC   -XX:+AlwaysPreTouch -XX:+UseLargePages   -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4   -jar server.jar nogui

This configuration assumes you have a dedicated server with at least 16 GB of physical RAM, NVMe storage, and a CPU with a Geekbench 6 single-core score of 2,000+. If you are shopping for hardware to run a modded Minecraft community, compare dedicated server plans for gaming on our comparison page to find a configuration that matches the RAM and CPU requirements above.

Remember: the best JVM tuning in the world cannot fix a server that is oversold on RAM or running on a CPU with single-core performance below 1,800. Start with the right hardware, then apply these flags. Your players will notice the difference before the first chunk loads.

Related Articles：

Dedicated Server Buying Checklist: 12 Specs to Verify Before You Sign Palworld Dedicated Server Hosting: Hardware Requirements and Optimization Guide Dedicated Server Bandwidth Management for Game Streaming Factorio Dedicated Server: CPU, UPS, and RAM Requirements for Megabases