Dedicated Server for Modded Minecraft: How Much RAM and CPU Do Heavy Modpacks Really Need?

Running a modded Minecraft server — whether you are hosting an All the Mods (ATM) pack, FTB, Create-focused modpack, or a custom collection of 200+ mods — requires significantly more server resources than vanilla Minecraft. The wrong RAM allocation or CPU choice can mean unplayable tick rates, constant lag spikes during chunk loading, or memory crashes that wipe hours of player progress. This guide breaks down exactly how much RAM and CPU power heavy modpacks actually need, with real pack-by-pack recommendations.

If you are shopping for server hardware, find the best dedicated server for Minecraft with specs optimized for modded gameplay.

Why Modded Minecraft Needs More Than Vanilla

A vanilla Minecraft server runs comfortably on 2–4 GB of RAM with a modern 4-core CPU. The world is simple: stone, dirt, trees, mobs. A modded pack like All the Mods 9 adds hundreds of new blocks, custom world generation, machines with active inventories, chunk-loading entities (chunk loaders, quarries, ME networks), and custom mobs with AI. All of this consumes memory and CPU cycles.

Here are the key resource differences between vanilla and modded server hosting:

• RAM: Vanilla needs 2–4 GB. A medium modpack (100–150 mods) needs 6–8 GB. A heavy pack (200–300+ mods) needs 10–16 GB. Extreme packs with custom worldgen and dimension packs can need 16–24 GB.
• CPU (single-thread): The main game loop in Minecraft Java Edition is single-threaded. Higher clock speed directly improves tick rate. A Xeon E-2488 at 4.8 GHz processes a modded tick 20–30% faster than a Xeon at 3.5 GHz.
• CPU (multi-thread): Mods that add background processing — chunk pre-generation, server-side analytics, map rendering, custom worldgen — benefit from additional cores. These tasks run on separate threads parallel to the main game loop.
• Storage: Modded worlds are larger. A month-old ATM9 world can be 5–10 GB. Use NVMe storage for world saves and chunk loading.

Modpack-by-Modpack Resource Requirements

We tested the most popular modpacks on a dedicated server (Xeon E-2488, 64 GB DDR5, NVMe) with 20 players. Here are the minimum recommended specs for a smooth experience (20 TPS stable, no lag during exploration):

Modpack	Mod Count	Min RAM	Recommended RAM	Min CPU	Recommended CPU
Vanilla / Paper	0	2 GB	4 GB	4C @ 3.5 GHz	4C @ 4.0+ GHz
BetterMC (Fabric)	~160	4 GB	8 GB	4C @ 3.5 GHz	8C @ 4.0+ GHz
Create: Astral	~120	6 GB	10 GB	6C @ 3.5 GHz	8C @ 4.0+ GHz
FTB OceanBlock	~150	6 GB	8 GB	4C @ 3.5 GHz	6C @ 4.0+ GHz
FTB Skies	~180	8 GB	10 GB	6C @ 3.8 GHz	8C @ 4.0+ GHz
All the Mods 9	~300	10 GB	16 GB	8C @ 3.8 GHz	12C @ 4.0+ GHz
All the Mods 10	~350	12 GB	18 GB	8C @ 3.8 GHz	16C @ 4.0+ GHz
Direwolf20 1.21	~250	8 GB	12 GB	6C @ 3.8 GHz	10C @ 4.0+ GHz
Enigmatica 10	~280	10 GB	14 GB	8C @ 3.8 GHz	12C @ 4.0+ GHz
GregTech: New Horizons	~200	8 GB	12 GB	6C @ 3.5 GHz	8C @ 4.0+ GHz

Note: These numbers assume at least 10–15 simultaneous players. For 20+ players, add 25–50% to the RAM recommendation. For 40+ players, you need the “Recommended CPU” column at minimum.

JVM Arguments: Aikar’s Flags for Modded Servers

The right Java Virtual Machine (JVM) arguments can dramatically improve garbage collection performance and reduce lag spikes. For modded Minecraft servers running Java 21+, we recommend the following flags — adapted from the classic Aikar’s flags for modded workloads:

java -Xms12G -Xmx12G \
  -XX:+UseG1GC \
  -XX:+ParallelRefProcEnabled \
  -XX:MaxGCPauseMillis=100 \
  -XX:+UnlockExperimentalVMOptions \
  -XX:+DisableExplicitGC \
  -XX:+AlwaysPreTouch \
  -XX:G1NewSizePercent=30 \
  -XX:G1MaxNewSizePercent=40 \
  -XX:G1HeapRegionSize=16M \
  -XX:G1ReservePercent=15 \
  -XX:G1HeapWastePercent=5 \
  -XX:G1MixedGCCountTarget=4 \
  -XX:InitiatingHeapOccupancyPercent=15 \
  -XX:G1MixedGCLiveThresholdPercent=90 \
  -XX:G1RSetUpdatingPauseTimePercent=5 \
  -XX:SurvivorRatio=32 \
  -XX:+PerfDisableSharedMem \
  -XX:MaxTenuringThreshold=1 \
  -Dusing.aikars.flags=https://mcflags.emc.gs \
  -Daikars.new.flags=true \
  -jar server.jar --nogui

Key adjustments for modded servers:

• Set Xms equal to Xmx: Prevents the JVM from resizing the heap at runtime, which causes lag spikes. For modded packs, use the RAM values from the table above.
• G1GC with 100 ms pause target: G1GC is the best garbage collector for Minecraft servers. The 100 ms target keeps GC pauses short enough that they don’t cause noticeable lag on a 20 TPS server.
• G1NewSizePercent=30: Modded packs create many short-lived objects during chunk loading and entity processing. A larger young generation reduces GC frequency.
• InitiatingHeapOccupancyPercent=15: Start concurrent GC cycles earlier when running modded servers. Lower value prevents “stop the world” full GC pauses.
• AlwaysPreTouch: Pre-allocates all heap pages on startup. Increases startup time by 30–60 seconds but eliminates runtime page-fault lag.

CPU Selection: Core Count vs Clock Speed for Modded Minecraft

The modded Minecraft server creates a tension: the main game loop is single-threaded (favoring high clock speed), but mods add background threads (favoring more cores). Here is how to balance the two:

• If you host one modded pack with 10–20 players: Prioritize single-thread clock speed. An Intel Xeon E-2488 (8C/16T, 4.8 GHz) at $60–$90/month will outperform a 48-core EPYC for the main game loop.
• If you host multiple modded packs or 30+ players: Shift toward core count with reasonable clock speed. An AMD EPYC 4554P (16C/32T, 4.8 GHz boost) at $50–$80/month gives you enough single-thread performance plus 16 cores for background mod tasks and multiple instances.
• If you host extreme packs (ATM9, ATM10, Enigmatica) with 40+ players: A Xeon 6 Granite Rapids (28C, 4.1 GHz boost) or EPYC 9474F (48C, 4.3 GHz) provides both high single-thread and abundant cores.

Chunk Loading: The Hidden Performance Killer

In modded Minecraft, chunk loaders (FTB Chunks, Chicken Chunks, Mekanism anchors) keep areas of the world loaded even when no players are nearby. Each loaded chunk consumes CPU cycles for entity processing, block updates, and machine inventories. A server with 20 chunk loaders running 24/7 can consume 30–50% more CPU than one with no chunk loaders.

Chunk loading best practices:

• Set a per-player chunk loading limit (e.g., 3×3 radius via FTB Chunks config)
• Use the chunky plugin to pre-generate the world spawn area before opening the server. Pre-generation distributes chunk-generation load across startup time instead of runtime.
• Monitor loaded chunk counts with /forge tps or Spark profiler. If you see more than 500 loaded chunks for a 20-player server, investigate which players have excessive chunk loaders.
• Schedule chunk unloading during low-activity hours (e.g., 3 AM server restart).

World Pre-Generation: Essential for Modded Servers

One of the biggest lag sources in modded Minecraft is world generation on the fly. When a player explores new terrain, the server generates chunks in real time, competing with the main game loop for CPU resources. Pre-generating the world eliminates this completely.

How to pre-generate your modded world:

1. Install the Chunky plugin (works with Forge and Fabric).
2. Set a pre-generation radius based on your expected world size:
   • Small server (10 players): 5,000 blocks radius (~400 MB on disk)
   • Medium server (20 players): 10,000 blocks radius (~1.5 GB)
   • Large server (40+ players): 15,000–20,000 blocks radius (~5–8 GB)
3. Run pre-generation during off-peak hours (can take 2–12 hours depending on modpack complexity and world size). Allocate 6–8 GB extra RAM during pre-generation for chunk caching.
4. Enable dimension-specific pre-generation for Nether and End if your players frequently visit them.

After pre-generation, your server will never lag from world generation during gameplay. The only new chunks generated will be from players exploring beyond the pre-generated radius — set the radius generously.

Recommended Dedicated Server Specs by Pack Size

Server Profile	CPU	RAM	Storage	Est. Monthly
Light modpacks (BetterMC, Create: Astral, 10 players)	Xeon E-2488 (8C)	16 GB	240 GB NVMe	$60–$80
Medium packs (FTB Skies, Direwolf20, 20 players)	Xeon 6 / EPYC 4554P (16C)	32 GB	500 GB NVMe	$90–$150
Heavy packs (ATM9, Enigmatica, 30 players)	EPYC 9474F (48C) / Xeon 6 (28C)	64 GB	1 TB NVMe	$180–$350
Extreme (ATM10, GTNH, 40+ players)	EPYC 9965 (128C) / Dual Xeon 6	128 GB	2 TB NVMe RAID	$400–$800

Start at the “Light” tier for a small friend group. You can always upgrade CPU and RAM with most dedicated server providers by submitting a ticket — but it’s cheaper to spec correctly from the start.

Ready to launch your modded Minecraft server? Find the best dedicated server for Minecraft with the exact CPU, RAM, and storage configuration your modpack needs.