Saving resources: how to get the most out of a cheap VPS?
Greetings, friends!
Anyone who has ever used servers understands the following situation: you have a small pet project, a Telegram bot, a VPN, or a scraper, and you don't want to buy a powerful machine. You open the hosting price list, choose the most budget-friendly plan for a couple of euros per month (with 1 CPU core and 512 MB of RAM), and… face harsh reality. As soon as you launch any somewhat heavy application, the server freezes completely, and the logs display the infamous Out of memory (OOM) error.
But there are no bad servers—only unoptimized software. Even on a micro-VPS with 512 MB of RAM, you can stably run several services simultaneously if you know where to trim the appetite of the operating system. Also, keep in mind that you don't always need to purchase a traditional VPS if your project doesn't require 24/7 uptime; for such use cases, hourly cloud servers are an excellent option.
In this article, we will break down a step-by-step optimization plan, choose the right technology stack, and learn how to squeeze the maximum out of entry-level hardware.
Key Takeaways: Survival Secrets on Micro-VPS
Ditch control panels: Classic graphical control panels can consume up to 50-70% of a weak server's resources. The console (SSH) is your only choice. For instance, I frequently use servers with limited CPU cores and RAM running Ubuntu. I can confidently say that a control panel is not required; nearly everything can be managed via the terminal if you take a little time to master it.
Death to the heavy stack: Forget about the Apache + MySQL combination in standard configurations. Switching to Nginx + PHP-FPM (configured in
ondemandmode) will save hundreds of megabytes of memory, allowing you to run additional applications or automation scripts.A swap file is non-negotiable: On ultra-cheap hosting plans, Swap is not an performance-enhancement feature—it is a safety net that protects critical processes from crashing due to memory exhaustion.
Choosing the Right Tech Stack
The components of your IT infrastructure must be as lightweight as possible. Replacing just a few resource-intensive services with efficient alternatives will free up crucial space in RAM.
Tech Stack Comparison Table
| Stack Component | Heavy Solution | Lightweight Alternative | Clean Memory Savings |
| Web Server | Apache | Nginx / Caddy | from 100-150 MB RAM |
| Database | MySQL 8.0 | SQLite / PostgreSQL | from 200-300 MB RAM |
| Docker Base Image | ubuntu:latest | alpine:latest | 10x reduction in image footprint |
Step-by-Step Micro-VPS Optimization Plan
1. Cleaning up the OS clutter (1-2 minutes)
Deploy a clean minimal install of Debian 12 or Ubuntu 24.04. Immediately remove Snap (it voraciously consumes RAM) and disable unused background daemons like cloud-init. This frees up to 100 MB of memory right at system boot.
2. Creating and configuring a SWAP file (1 minute)
If your instance has 512 MB of RAM, create a Swap file of at least 1-2 GB. Even on budget storage drives, this baseline safety measure will prevent database crashes and keep critical processes safe from the OOM-killer.
3. Setting process resource constraints (3 minutes)
In your database configurations, strictly define resource limits (lower the innodb_buffer_pool_size buffer value to 64-128 MB) and switch PHP-FPM to a dynamic, on-demand operational mode.
Practical Guide: Creating Swap and Setting Up PHP-FPM
We have recorded a video showing the entire optimization workflow:
Execute the following commands sequentially in your terminal to provision a 1 GB swap file and reduce the kernel's swap aggressiveness (swappiness = 10):
sudo fallocate -l 1G /swapfile && sudo chmod 600 /swapfile && sudo mkswap /swapfile && sudo swapon /swapfile
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
echo 'vm.swappiness=10' | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
In your PHP-FPM pool configuration file (www.conf), switch process management to "on-demand" mode. If no visitors access the site, PHP will completely unload its active worker processes from memory after 10 seconds of idle time:
pm = ondemand
pm.max_children = 4
pm.process_idle_timeout = 10s
FAQ: Quick Summary
Can I run Docker on 512 MB of RAM?
Yes. Docker shares the host system's kernel and does not consume significant memory overhead by itself. The key requirement is to build your containers using Alpine Linux base images and avoid heavy runtimes (like Java or .NET).
What is swappiness and why should it be modified?
The
vm.swappinessparameter defines how aggressively Linux moves memory pages from RAM into the Swap file. The default value is 60. Lowering this value to10ensures that the operating system only utilizes disk-based swap during critical memory shortages, maintaining optimal application performance in native RAM.
Conclusion
Avoiding bulky control panels, configuring a swap file, and enforcing strict process limits will allow your project to remain stable and scale even on minimal compute resources without unnecessary expenses. If you are looking for a flexible hosting platform to deploy micro-projects or spin up servers with flexible hourly billing, explore our services at MivoCloud.
Article Author — Anatolie Cohaniuc