From VPS to VDS: when is it time to make the switch?

You once started out with a small VPS and that worked fine. But by now it's running more than you ever planned: your game server has grown, a database was added, maybe a bot and a website. And now you're noticing the squeeze. The big question: do you upgrade to a bigger VPS, or is it time for a VDS with dedicated cores?

This isn't a matter of "more expensive is always better". A VDS solves one very specific problem. If you don't have that problem, you're paying for something you're not using. Below you'll see exactly where the difference lies, which signs tell you your VPS is getting too small, and how to handle the move without losing your players.

Shared or dedicated cores: here's the difference

A VPS (virtual private server) and a VDS (virtual dedicated server) look very similar on paper. Both are virtual machines on a physical server, with their own RAM, their own storage and their own operating system with root access. The difference is in the CPU.

With a VPS you share the physical CPU cores with other customers on the same machine. You're assigned vCPUs, but they're not exclusively yours. As long as not everyone floors it at the same time, you won't notice a thing, which is exactly why a VPS is so cheap: the host can divide the same hardware efficiently. If you (or your neighbour) push the cores hard for long periods, things have to be shared out, and then your server may end up waiting at exactly the wrong moment.

With a VDS the cores are reserved exclusively for you. Nobody else runs on your cores, so your performance is predictable, even if you load them at 100% day and night. That's exactly why doing so is simply allowed on a VDS, whereas virtually every host applies a fair-use limit on sustained maximum CPU load for a VPS.

In short: a VPS buys capacity that is usually there, a VDS buys capacity that is always there.

Signs your VPS is getting too small

Wondering whether you're hitting the limits of your VPS? These are the classic symptoms:

• Lag at peak times. Everything runs smoothly during the day, but in the evening when everyone is online your Minecraft server drops below 20 TPS or your FiveM server starts to stutter. Peak hours are precisely when shared cores become scarce.
• CPU steal time. Look at the st column in top or htop. It shows how often your virtual machine had to wait for the physical CPU. If it's consistently above a few percent, you're noticeably competing with your neighbours.
• Restarting "helps". If a reboot only briefly boosts performance each time, that's often a sign the underlying capacity is simply used up.
• Optimizing yields nothing anymore. You've trimmed plugins, lowered view distance, cleaned up scripts, and it barely makes a difference anymore.
• Performance varies for no apparent reason. Same load, but fast one moment and slow the next: that points towards congestion on the host, not towards your configuration.

Do pay attention to which limit you're hitting. If your RAM is full or your storage is overflowing, you need a bigger plan, but not necessarily dedicated cores. A VDS specifically solves the CPU problem: compute time that isn't there at peak moments.

Who a VDS really makes sense for

In practice we see four situations where the switch pays off:

• Large FiveM servers. Lots of players and dozens of resources make FiveM notorious for its CPU appetite, and consistent single-core performance in particular determines how smooth your server feels. Dedicated cores take the volatility out of that.
• Minecraft networks. If you run a proxy with multiple servers behind it (survival, creative, minigames), you have multiple Java processes all demanding compute time at once. On reserved cores you can divide them neatly without them getting in each other's way, or in anyone else's.
• A complete community stack on one machine. Game server plus database plus website plus bots: the more you stack, the more painful unpredictable CPU capacity becomes.
• Events and competitive play. During a tournament or stream event you don't want to gamble on whether the host happens to be busy that evening.

The plans and prices at a glance

At MC-Node, a VDS runs on the same in-house hardware as the rest of the platform, in the Previder PDC2 data centre in Hengelo, with NVMe storage and DDoS protection. These are the plans:

Worth knowing: the heaviest VPS (HEN-B-11) costs €25.70 per month and the entry-level VDS €28.00. If you're already at the top of the VPS range, the price difference is barely a hurdle, while you get guaranteed cores in return. All plans can be cancelled monthly, so you're not locked into anything if the switch turns out to be premature after all. Compare the options in the MC-Node VDS store and pick the memory that matches your current usage plus some room to grow.

How to handle the migration

A migration doesn't have to be a big drama if you do it in the right order:

1. Take stock of what's running. Services, ports, cron jobs, databases, firewall rules. Anything you forget now, you'll discover later at the worst possible moment.
2. Order the VDS alongside your current VPS. Because both can be cancelled monthly, you pay double for a short period at most. That's the cheapest insurance against downtime there is.
3. Move your data over. Copy files, make database dumps and restore them on the new machine.
4. Test first, go live afterwards. Start your server on the VDS and spend an evening playing on it yourself before inviting anyone else.
5. Switch the address over. If you use a (sub)domain as the server address, lower the DNS record's TTL beforehand and change the IP at the agreed moment.
6. Run in parallel briefly. Keep the old VPS around for a few more days as a safety net and only cancel it afterwards.

One tip that prevents a lot of misery: have players connect via a subdomain such as play.yourdomain.com instead of a bare IP address. Then every future move is a DNS change instead of a campaign to get everyone to enter a new address.

When you're better off not switching (yet)

Fair is fair: a VDS isn't the right step for everyone. If your CPU usage stays well below half even at peak times, you'll notice little from dedicated cores. There's also plenty of headroom within MC-Node's VPS range: the plans run from €2.00 to €25.70 per month, so an intermediate step to a bigger VPS is often cheaper than jumping straight to €28.00 or more.

Also check whether the problem really is the CPU. Full RAM, slow storage or one badly written plugin or script can produce the same symptoms. Profile your server first: if one component is eating all your compute time, that problem simply moves along to your new VDS. And remember that a VDS doesn't magically improve your configuration; it only guarantees that the compute power you buy is genuinely always there.

Still ending up at "my server structurally needs more and above all more predictable CPU" after those checks? Then the switch isn't a luxury but the logical next step, certainly with a player count that keeps growing.