If your site has started slowing down on shared hosting, if you need to install custom software, or if you have run into the phrase “root access required” in a piece of documentation, then a VPS is where you are headed. In this guide we cover what a VPS is, the logic behind virtualization, and how to choose CPU cores, RAM, and disk for your project, with concrete examples.
What is a VPS?
A VPS (Virtual Private Server) is an independent server with its own operating system and resources, created by dividing a physical server through a software layer. From the outside it behaves like a separate machine: it has its own IP address, its own disk, and its own memory, and you can install any software you want on it.
The fundamental difference from shared hosting is the level of control. With hosting you manage only your site files and your database through a ready-made panel; you cannot touch the server itself. On a VPS, root privileges are yours: you choose the operating system, install the PHP or Node.js version you want, and configure the firewall yourself.
The price of that freedom is responsibility. Updates, the backup routine, and security hardening are now in your hands. If you do not want to get into server administration at all, that may be the first sign a VPS is not right for you.
How does virtualization work?
At the center of it all sits a software layer called a hypervisor. The hypervisor slices up the physical server’s processor, memory, and disk, and distributes a share of each to every VPS. With full virtualization technologies such as KVM, each virtual machine runs in isolation with its own kernel; an error or a reboot on a neighboring server does not affect you.
By way of analogy, the physical server is an apartment building, the hypervisor is the building management, and each VPS is a separate apartment. You hold the key to your apartment and can paint the walls any color you like, but everyone shares the building’s electrical and water infrastructure.
In practice this architecture has two important consequences. First, your VPS is provisioned within minutes, and reinstalling it when needed is just as fast. Second, because resources are defined in software, upgrading a plan is usually a matter of a short reboot; you do not wait for a hardware swap the way you would on a physical server.
The difference between VPS and VDS
These two terms are frequently confused in Turkey’s hosting industry. On a VPS, resources can be shared out flexibly, while on a VDS (Virtual Dedicated Server) CPU cores and RAM are allocated directly to you; your performance does not change when neighboring servers get busy. For projects that need consistent performance, SSD VDS plans offer options starting at 44.99 TL/month; for the classic setup, you can look at the VPS plans.
Which projects is a VPS suitable for?
A VPS is a sensible middle stop for any project that says “shared hosting is not enough, but a physical server is too much.” Typical scenarios are:
- Growing WordPress or WooCommerce sites: You can set up a caching layer (Redis, Varnish) and fine-tune PHP settings to match your traffic.
- Custom software and API servers: You run the application you wrote in Node.js, Python, or Go in your own environment.
- Test and staging environments: You can try new versions on a real server before going live.
- Services such as VPN, game servers, and Telegram bots: Ideal for small but continuous workloads that need to stay up 24/7.
There is another side to the coin. For a single brochure site receiving a few thousand visitors a month, the management overhead of a VPS is unnecessary; Linux hosting starting at 19.99 TL/month handles that job more than adequately. For projects with constantly high CPU usage and large databases, a dedicated server, which removes the virtualization layer entirely, is the better fit.
Choosing resources: calculating cores, RAM, and disk
The most common mistake when choosing a plan is the “let me take the cheapest one and see later if it is not enough” approach. In fact, a rough calculation makes it possible to pick the right plan the first time. If you already have a server, you can see current usage with three commands:
free -h # memory usage
nproc # number of cores
df -h # disk usageExample: a medium-traffic WordPress site
Consider a WordPress installation running Nginx + PHP-FPM + MySQL. Set aside roughly 1 GB so MySQL can work comfortably. Each PHP-FPM worker consumes an average of 60-80 MB of memory; to serve 15 simultaneous requests you need 15 × 80 MB ≈ 1.2 GB. Leave another 1 GB for the operating system and the file cache.
That comes to roughly 3.2 GB in total, which means a plan with 4 GB of RAM is a comfortable choice for this site. Squeezing it into 2 GB is possible, but when traffic fluctuates the first thing to fall over is usually the database. Adapt the same calculation to your own stack: list the typical memory consumption of every service you will run, one under the other, and add a safety margin on top.
How do you determine cores and disk?
Core count is about concurrency: for mostly website-oriented workloads, 2-4 cores are enough for most projects; for CPU-heavy work such as video processing, intensive cron jobs, or game servers, go up to 6-8 cores. With disk, look at the technology rather than the capacity: NVMe SSD makes a noticeable difference over classic SATA disks on database queries. When calculating capacity, use the formula site files + database + free space for at least one full backup.
Quick decision table
| Scenario | Cores | RAM | Disk (NVMe) |
|---|---|---|---|
| Blog, brochure site, bot | 1-2 | 2 GB | 20-40 GB |
| Corporate site + email | 2 | 4 GB | 40-60 GB |
| WooCommerce, medium-traffic e-commerce | 4 | 8 GB | 80-120 GB |
| Heavy API, game server, multi-site setup | 6-8 | 16 GB | 150 GB+ |
Checklist before you rent a VPS
Plans look alike on paper; the infrastructure is what makes the difference. Before you rent, ask these four questions: Where is the data center? If your visitors are in Turkey, a server in an Istanbul location delivers noticeably lower latency than one abroad. Is the uptime commitment in writing? Is the disk NVMe? When a problem comes up at 3:00 a.m., who will you reach?
SunucuCenter’s VPS servers run in the Equinix data center in Istanbul, on NVMe SSD infrastructure with a total network capacity of 80 Gbit/s; a 99.98% uptime commitment and 24/7 support back the service.
One last suggestion: after you finish your resource calculation, look at the price difference with the next plan up. If the gap is small, buying room to grow from the start is a cheap way out of the trouble of migrating later.
Frequently asked questions
How do I connect to a VPS?
On Linux servers you connect from the terminal with the ssh root@server-ip-address command, and on Windows servers you connect with Remote Desktop Connection (RDP). Connection details are sent by email when the server is delivered.
If my resources run short, can I upgrade later?
Yes. This is the most practical aspect of virtualization: cores, RAM, and disk can be increased by moving to a higher plan without reinstalling the server. That is why choosing the plan that fits your calculation and growing as the need arises is more economical than buying a huge plan at the start.
Is managing the VPS my responsibility or the provider’s?
On standard (unmanaged) plans, the hardware, network, and virtualization layer belong to the provider; the operating system and everything on top of it are your responsibility. If you have no experience in server administration, it is worth asking the support team about management support options before you buy.
Leave a Reply