Minecraft Modpack Server Hardware Sizing (2026)
"Will an i3-9100 handle a server for 8 friends running Cobbleverse?" is the question that lands in r/admincraft about twice a week. The answer is almost always "no, but here's what will." This page gives realistic 2026 numbers for the most-played modpacks, with both boot-time and steady-state numbers, plus why your CPU choice matters more than your core count.
How modpack load actually scales
A Minecraft modded server with 200 mods doesn't just need 4x the RAM of vanilla — it's more like 4-8x baseline plus exponentially more during chunk-load events. The factors that drive load:
- Mod count: Each mod registers blocks, items, recipes, entities at boot. Boot RAM scales linearly.
- World-gen complexity: Heavy biome mods (Terralith, Biomes O'Plenty) increase per-chunk gen cost.
- Per-tick entities: Mod-added mobs, machines, conveyors all tick every server tick.
- Per-player chunk radius: 8 players × 32 chunks each = 256 chunks loaded (overlap reduces actual count but still big).
- Magic / tech crossover: Some mods proxy block updates across dimensions (Botania, Mekanism), multiplying tick cost.
Per-modpack 2026 sizing reference
| Modpack | Boot RAM | Steady-state RAM (5 players) | Peak RAM | Recommended CPU |
|---|---|---|---|---|
| Vanilla 1.21 | 1-2 GB | 3-4 GB | 5-6 GB | 4 cores, 3.5GHz+ |
| Paper + 10 plugins | 1-2 GB | 3-5 GB | 6-8 GB | 4 cores, 4.0GHz+ |
| Cobbleverse (~250 mods) | 8-10 GB | 12-14 GB | 18-20 GB | 6 cores, 4.5GHz+, large L3 |
| All The Mods 10 (~400 mods) | 10-12 GB | 14-16 GB | 22-24 GB | 6+ cores, 4.5GHz+, large L3 |
| Better MC (~180 mods) | 6-8 GB | 10-12 GB | 16 GB | 4 cores, 4.5GHz+, large L3 |
| FTB Skies (~150 mods) | 5-6 GB | 8-10 GB | 14 GB | 4 cores, 4.5GHz+ |
| RLCraft (~140 mods) | 5-7 GB | 9-11 GB | 15 GB | 4 cores, 4.5GHz+, large L3 |
| Create: Astral / Create-heavy packs | 6-8 GB | 10-14 GB | 20 GB | 6+ cores, 4.5GHz+ (Create AI is expensive) |
| Vault Hunters 3 | 6-8 GB | 10-12 GB | 16 GB | 4 cores, 4.5GHz+ |
| SkyFactory 5 / SkyBlock packs | 4-6 GB | 7-9 GB | 12 GB | 4 cores, 4.0GHz+ |
| Pixelmon | 6-8 GB | 10-12 GB | 16 GB | 4 cores, 4.5GHz+ |
Steady-state assumes 5 active players. Add roughly 1-2 GB per additional active player. Peak RAM occurs during world-gen events, large mob spawns, or auto-save.
Not sure where to land for your pack and player count? Our Minecraft server RAM & JVM-flags calculator turns those numbers into a recommended -Xmx plus a ready-to-paste startup command with Aikar's tuned G1GC flags.
About these numbers: they are general estimates derived from each pack's mod count and community-reported figures, not Supercraft-tested guarantees. A world's real needs grow with exploration, automation, world size, render/simulation distance, and player count - treat the ranges as a floor and size up for a busy server.
Why "8GB should be enough" is the most common mistake
The standard r/admincraft mistake: someone reads "Cobbleverse: minimum 6GB" on the modpack's CurseForge page and provisions an 8GB plan. The result is fine for 1-2 weeks, then:
- Players explore further; new chunks load; RAM ticks up.
- Tech mods build up automated systems with persistent state.
- Garbage collection becomes more frequent (because heap is closer to limit).
- GC pauses get long enough to hit "Can't keep up" warnings in the server log.
- TPS drops below 20; gameplay becomes unplayable.
The modpack's stated "minimum" is for one player starting a fresh world. Multiplayer steady-state needs are 2-3x that.
CPU matters more than you think
People obsess over RAM, but for modded servers, CPU single-thread performance is more often the limiting factor. Symptoms of CPU bottleneck (vs RAM):
- TPS drops below 20 with plenty of free RAM available.
- Server feels laggy even when memory monitor shows 30% headroom.
- "Can't keep up" messages in console even though heap is fine.
If you see these on a server with plenty of RAM, your CPU isn't fast enough for the per-tick work. Move to a faster CPU (or accept lower mod count / fewer players).
What actually matters: per-core clock and L3 cache
For modded Minecraft the two CPU traits that matter most are high per-core (single-thread) performance and a large L3 cache. The server's hot paths thrash the cache hard with hundreds of mods loaded, so cache that holds the working set helps as much as raw clock. On the desktop, AMD's 3D V-Cache (X3D) chips like the 5800X3D and 7950X3D are the well-known example - in community benchmarks a 5800X3D at 4.5GHz often keeps pace with higher-clocked non-cache chips on modded MC.
Managed hosts run server-grade silicon rather than desktop parts. Supercraft's nodes are AMD EPYC (24c/48t+, large L3 cache, 512 GB RAM, NVMe) - the core count, cache and memory headroom let us run large heaps and dense modded workloads, and we size the plan to the pack rather than chasing a single desktop clock figure.
Storage matters too (NVMe SSD recommended)
Chunk loading hits disk. With 200+ mods, each chunk references far more block IDs and entity types, making disk I/O significantly more frequent. Modded servers really benefit from NVMe SSD:
- HDD: Don't. Chunk load times become unplayable.
- SATA SSD: Adequate for small modpacks (< 100 mods).
- NVMe SSD: Required for large modpacks. ~5-10x faster chunk loads.
The "i3-9100 for 8 players" scenario
Now we can answer the original r/admincraft question. An i3-9100 has 4 cores at 4.2GHz boost, no X3D, dual-channel DDR4 likely DDR4-2400 or 2666. Verdict:
- Vanilla 8 players: Just barely. Will run fine until the world grows.
- Paper + light plugins: Acceptable.
- Cobbleverse / 200+ mods, 8 players: No. The CPU will be saturated within the first hour.
- Cobbleverse, 2-3 players: Maybe, if you accept occasional lag.
For 8 players on a heavy modpack, the minimum 2026 spec is a Ryzen 5 5600 / i5-12400 with 16GB RAM and NVMe SSD. The Ryzen 5 5800X3D would meaningfully better that.
Plan-tier translation
If you're shopping managed hosting, here's how modpack scenarios map to typical plan tiers:
| Scenario | Plan tier | Approximate price (2026) |
|---|---|---|
| Vanilla, 5-10 players | Plan S (4 GB RAM) | from $5.99/mo |
| Paper / Purpur + plugins | Plan M (6 GB RAM) | $9.99/mo |
| Lighter modpacks / smaller groups that fit in 8 GB | Plan L (8 GB RAM) | $16/mo |
| Heavy modpacks above 8 GB steady-state (Cobbleverse, ATM10, Better MC) | Custom high-memory plan | contact support for a quote |
Recurring sizing mistakes
- Provisioning based on the modpack's CurseForge minimum. Those figures are for one player on a fresh world; multiplayer steady-state runs well above them, so build in real headroom.
- Equating RAM with performance. CPU single-thread clock is equally critical.
- Forgetting that mods grow. Many modpacks add mods through patches; today's 4GB allocation isn't tomorrow's.
- Setting
-Xmxequal to total system RAM. Leave 1-2GB for the OS and other processes. - Skipping NVMe. SATA SSD is acceptable but NVMe is real-world faster for chunk loads.
Related guides
- Aikar's flags (JVM tuning)
- General server optimization
- Modding guide (mod installation)
- Server software comparison
- Choosing a dedicated host
Need a Minecraft server sized for a real modpack? Supercraft Minecraft Java hosting runs on AMD EPYC server hardware (large L3 cache, 512 GB RAM nodes, NVMe SSD) with instant Java 21/26 switching and Paper/Purpur/Folia/NeoForge support. Plans from $5.99/mo, with custom high-memory plans for the heaviest packs.