At some point most growing servers ask the same question: is it time to move off a shared plan and onto dedicated hardware. This post explains what the two actually mean, when shared is genuinely the right choice, the signs that you have outgrown it, and what dedicated buys you. The honest answer for a lot of people is "not yet", so we will say that where it is true.
What the words mean
Shared hosting puts several game servers on the same physical machine. You get a slice of its cores, memory and disk, managed so that each tenant stays in its own container. It is the standard way to host a small server, and when the machine is not oversold it works well.
Dedicated hosting gives you the whole machine, or a reserved block of it that nobody else touches. The cores are yours, the RAM is yours, and the cache on the chip is working for your server alone. You are paying for hardware that sits ready for you whether you are using all of it this minute or not.
The important detail sits underneath both: whether the resources are reserved. A well-run shared plan with reserved cores and RAM can beat a badly-run one every day. If you have not read it yet, our guide on spotting overselling in game hosting covers how to tell a reserved plan from an oversubscribed one, and it matters as much as the shared-versus-dedicated question itself.
When shared is genuinely fine
Plenty of servers never need to move, and telling everyone to buy the biggest thing would be dishonest. Shared hosting is the right call when:
- You run a small server for friends, with a handful of players online at once.
- Your player counts are low and fairly steady, without big login waves.
- You are running vanilla or a light plugin set rather than a heavy modpack.
- You want the lowest sensible monthly cost and can accept that a busy evening might occasionally feel less than perfect.
If that describes you, a reserved shared plan is not a compromise you will regret. It is the efficient choice, and you can always move up later. Spending more than you need on idle cores helps nobody.
The signs it is time to move up
The picture changes as a community grows. A few signals tell you that shared is starting to hold you back:
- The player count keeps climbing. More concurrent players means more entities, more chunk loading and more work per tick. At some point the single tick thread needs a faster core and more cache than a shared slice comfortably gives it.
- You are running big modpacks. Heavy modded Minecraft is demanding on both memory and single-thread performance. Large packs want reserved RAM so garbage-collection pauses stay short, and they want a core that is not being shared at the busy hours.
- You want consistent TPS. If holding a steady 20 TPS through your peak has become the thing you care about most, you want headroom that a shared plan is not designed to guarantee.
- You want full control. Custom JVM flags, a specific garbage collector, a performance fork, more aggressive tuning: dedicated hardware gives you room to make those choices instead of living inside a fixed slice.
If two or three of those are true at once, the upgrade will probably pay for itself in fewer lag complaints.
What dedicated actually gives you
Moving to dedicated hardware changes a few things in ways you can measure.
Reserved cores and RAM are the headline. The main loop gets a full-power core to itself, so a busy evening does not turn into tick jitter, and the memory you were promised is genuinely there when a modpack spikes.
The X3D cache advantage is a dedicated-only story, so we will scope it honestly. On a dedicated server, where you are not sharing the chip, you can have a large-cache AMD X3D part. Game ticks are cache-bound, meaning the main thread spends much of its time waiting on memory, and keeping the hot working set resident in a large cache cuts tick time more than extra clock speed does. That gain only exists when you own the whole chip, which is why it belongs to dedicated rather than shared. Our guide on choosing a CPU for Minecraft goes deeper on why cache matters so much for this workload.
Background work is the other gain. Paper, and the performance mods on a modded server, push chunk loading, generation and lighting onto worker threads. On a shared slice those threads compete with every other tenant for the same cores. On a dedicated box they land on cores that are actually free, so world loading stops eating into the tick.
How to decide
Start with what your server is doing today, not what you hope it will do next year. If you have a small, steady group on a reserved shared plan and the tick holds through your peak, stay where you are and put the money elsewhere. If your community is growing, your packs are getting heavier, and consistent TPS has become the thing you fret about, dedicated is the upgrade that fixes the actual bottleneck rather than papering over it.
Either way, the resources being reserved matters more than the label on the plan. Pick reserved, then pick the size that matches the load you really have.