What a VPS Is, And When You Actually Need One

A number from our own server

The machine serving this page has four processor cores and eight gigabytes of memory. Nine live WordPress sites run on that single box, and the system load average at the moment of writing was 0.4, which is roughly a tenth of capacity.

We mention it because VPS vendors talk in cores and gigabytes, and that is not what runs out first. What runs out first is the number of PHP processes that can execute at the same time.

What actually brings a server down

On this machine pm.max_children is set to twenty. Twenty PHP requests execute concurrently and everything else waits in a queue.

Now picture a situation we have lived through: the cache for an entire site gets cleared. Every page without a cached copy has to be rebuilt by PHP, and if a hundred URLs are requested at once, twenty run and eighty queue. The site slows for everybody, including the eight other sites that had nothing to do with it.

The processor is idle throughout. Memory has room. What ran out was the queue. That is why upgrading from two cores to four does not fix this, and getting the cache layer right does.

When a VPS is genuinely the answer

Four situations where it is not a close call.

You need software other than WordPress. If you have to run Node, Redis or a background service, shared hosting will not let you and the discussion is over.

The neighbours are hurting you. If you are on shared hosting and your server response time climbs at particular hours without anything changing on your side, the problem is probably not you.

You hold sensitive data. For a site storing customer information, an isolated environment is worth having even if you never use the resources fully.

You run several sites. Past three or four, one VPS usually works out cheaper than several separate shared plans, and easier to administer.

When it is not

If you have one WordPress site taking a few thousand visits a day and its page cache works properly, a VPS adds nothing except a list of jobs you now have to do.

Nobody itemises those jobs at the point of sale: operating system security updates, firewall configuration, backups, certificate renewal, and monitoring whether the server is even up. On shared hosting the host does all of that and it is priced in.

Buying a server to fix slowness

There is a more common trap as well: buying a VPS to fix a speed problem. If your site is slow because the page weighs three megabytes, or because a plugin rebuilds everything on every request, the same site will be exactly as slow on a more expensive server. The real relationship between hosting configuration and speed separates the part of the slowness that is the server's fault from the part that is not.

Managed or unmanaged

This distinction matters more than the core count and it rarely appears in the pricing table.

An unmanaged server is an empty machine, and from the moment it is handed over anything that breaks is yours. A managed server means the host handles updates, backups and basic security, and it costs more for the obvious reason.

If you are not comfortable on a Linux command line, an unmanaged server is not cheap. You have simply converted the cost from money into your own time. The first night the site goes down at two in the morning, you will run that conversion again.

Questions people ask

Is a VPS faster than shared hosting? Not necessarily. A weak, untuned VPS is slower than a good shared plan. Speed comes from configuration, not from the product category.

How much memory do I need? For one to three ordinary WordPress sites, two gigabytes is enough. If someone tells you that you need eight, ask them what they are basing that on.

Iranian server or foreign? If your audience is in Iran and you are paying in rial, domestic usually makes more sense. The comparison we ran between two Iranian hosts shows the gap between two domestic providers can be wider than the gap between domestic and foreign.

If you are unsure which group you are in, the simplest move is to find out where your current site actually loses time. For most sites the answer is not the server, and choosing hosting that matches your real traffic works out cheaper than upgrading blind. If you do run several sites or need particular software, WordPress hosting with the configuration already done is a sensible middle point. And for a site built heavy from the beginning, no server substitutes for rebuilding it with a lighter structure.

The server specification and the pm.max_children value were read from that machine on 15 August 2026. They describe our own configuration rather than a recommendation that holds for every server.