HomeBlog
How to Choose a VPS for a Website or Application

How to Choose a VPS for a Website or Application

Your website was fast until you added a product catalog and background stock updates. Now pages load more slowly, even though the number of visitors has barely changed.

To understand how to choose a VPS, start with the tasks. Below we explain how VPS resources are connected, give starter configurations and show when it makes sense to change them.

Which VPS resources affect performance

The CPU does the computing: it runs code, handles database queries and creates archives. The number of vCPUs shows how many virtual processors you have, but it does not determine speed on its own: the CPU model, how processor time is shared and the nature of the task all matter.

For example, generating images loads the processor differently from serving ready-made HTML files. A single slow sequential process may not get faster with more cores if the program cannot work in parallel.

RAM holds the data of active processes. The operating system, web server, application and database all need it. The disk cache also uses memory, but the system can free it for other needs.

“A good choice starts with understanding your own task.”

A disk has two separate characteristics: capacity and speed. There must be enough capacity for the OS, files, database, logs and temporary data. Speed affects read and write latency.

Evaluate the network by port speed, available traffic and the route to your audience. A 1 Gbps port does not mean every visitor will download a file at that speed. Write down exactly what your server will be doing.

Which configurations to start testing with

The numbers below are our editorial guidelines for testing, not a guarantee of performance or the names of FOTBO plans. They apply to small Linux projects without a heavy control panel, with the database and application running on the same VPS.

TaskStarting point for a testWhat to measureWhen to review
Static website1 vCPU, 1–2 GB RAM, 20 GB diskResponse time and network trafficFile volume or data transfer grows
Small CMS website2 vCPU, 2–4 GB RAM, 30–40 GBResponse time, RAM, DB queriesPeaks slow responses down even after optimization
Small online store2–4 vCPU, 4–8 GB RAM, 50 GB or moreCatalog, cart, background jobsRequest queue builds up or RAM runs out
Simple bot1–2 vCPU, 1–2 GB RAM, 20 GB or moreEvent queue and process memoryEvents are processed with a delay
Small web application2 vCPU, 4 GB RAM, 30 GB or moreAPI response, errors, databaseTarget response time is not met

These ranges do not cover heavy analytics, local AI models or large media libraries. Such tasks need a separate calculation. Start with a test deployment of your own software.

How much RAM a VPS needs

How much RAM a VPS needs depends on the number of processes running at the same time. Take into account the system, database, cache, control panel and background services. A small website with many plugins can use more memory than a simple application.

For example, if one worker process takes about 150 MB, ten such processes will need roughly 1.5 GB for themselves alone. This is a rough calculation: the value has to be measured on your own program.

Run free -h and look at the available column. It estimates how much memory can be given to new programs without swap. Do not draw conclusions from the free column alone: the Linux cache can use free RAM for a good purpose.

Swap is disk space the system can use for some memory pages. It is no substitute for RAM in terms of speed. Regular swapping under load combined with slow responses needs diagnosing.

If a process keeps growing even without requests, check for a memory leak first. Buying a bigger plan will delay the failure but will not remove the cause. Take measurements before, during and after the peak.

How to evaluate disk and network

Start with real data: the website files, the database size and a week's worth of logs. Add space for updates, temporary archives and growth. The right margin depends on how fast things change, not on a universal percentage.

For example, the catalog takes 8 GB, the database 3 GB, and logs add 1 GB a week. Without log rotation, even a disk that is large enough at the start will fill up. Set retention periods and free-space alerts.

The df -h command shows file system capacity, and df -i shows inode usage, which is how files are tracked. There may still be space in bytes when there is nowhere left to register new files.

For a slow disk, check latency with iostat -xz 1 5. Compare it with the application's response time; a single device utilization figure does not explain every case.

For the network, it matters whether you serve pages, video or large archives. The volume of transferred data and latency are different things. Record both parameters for your own scenario.

How the database and cache change the requirements

A database needs memory for its working data and disk space for storage. A poorly written query without the right index can load the CPU and disk even with a small number of users.

Caching a ready-made page cuts repeated work. However, the cart, the user account area and personal prices cannot be cached as carelessly as a public product description. Check that the result is correct, not just fast.

“Measurements turn assumptions into decisions.”

Before changing the configuration, compare slow queries, the number of processes and background jobs. If a backup runs at the same time as a catalog import, rescheduling it may remove the peak without a new plan.

The article “How to Check VPS Performance” describes a separate testing method. At this stage, it is enough to collect basic metrics and find the resource that limits your work.

When to increase VPS resources

Vertical scaling means adding CPU, RAM or disk to a single server. Before making the change, check your provider's procedure: whether a shutdown is needed, whether the file system expands and whether you can go back to a smaller configuration.

Horizontal scaling adds servers. It requires sessions, files, the database and load balancing to work together. For a small project, such a setup can be more complex than upgrading a single VPS.

Gather this information before changing your plan:

  • which pages or operations slow down;
  • which resource runs out during the peak;
  • whether caching and query tuning helped;
  • how much headroom you need for expected growth.

After the change, repeat the same scenario. This way you will see whether the new VPS resources helped, rather than a random difference in load.

How to choose a VPS for your project

Review the VPS configurations and compare them with your test results. The current VPS pricing will help you evaluate your chosen option without tying this article to prices that change.

Now you know how to choose a VPS based on real tasks and how to work out how much RAM a VPS needs. Start with a measurable scenario, leave a reasonable margin and review the configuration as your project grows.

How to Choose a VPS for a Website or Application
vds

You might be interested in Fotbo's VPS server

View