All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Small WordPress site on a low-end VPS: what specs and stack would you pick?
Hi everyone,
I’m planning to move a small WordPress site to a low-end VPS and want to avoid overspending or choosing a stack that struggles.
The site:
WordPress with a custom theme and a few plugins
Low traffic for now, a few hundred visits a day at most
Mostly static pages, with no online store
What I’m considering:
1 vCPU, 1 to 2 GB RAM, 20 to 40 GB NVMe or SSD
No control panel, managed over SSH
Nginx + PHP-FPM + MariaDB, with a caching plugin
My questions:
is 1 GB RAM enough for WordPress with Nginx + PHP-FPM + MariaDB, or should I start at 2 GB?
Do you recommend a full-page cache (FastCGI cache or a plugin), or is that overkill at this traffic level?
For a visitor base in South Asia, does the VPS location matter much, or does a CDN like Cloudflare solve most of it?
What’s the first security hardening step you’d do on a fresh VPS (SSH keys, firewall, fail2ban, something else)?
I’d appreciate hearing what setup works for you, especially if you run a similar small site.
Thanks!
Comments
1 GB can work if you add a swap file and keep PHP-FPM to a few workers, but 2 GB gives MariaDB room to breathe and is usually only a dollar or two more.
Start there and save yourself the headache. At a few hundred visits a day a caching plugin is plenty - FastCGI cache is faster, but clearing it after you update a page is one more thing to manage. Not worth it.
For South Asia, pick a VPS in Singapore or Mumbai if you can. Cloudflare helps with images and CSS, but by default it still fetches each page from your server, so the distance still shows up.
On a fresh VPS, start with SSH keys and turn off password login, then the firewall (only 22, 80 and 443 open) and automatic security updates. Fail2ban after that. And set up backups before you need them!
2 GB if you can stretch to it, honestly. I ran a small site on 1 GB for a while and it works, but you end up watching memory instead of writing content. The two settings that made the biggest difference for me on 1 GB were MariaDB's innodb_buffer_pool_size, which I set to 256M, and PHP-FPM on ondemand with max_children at 5. The defaults just eat RAM for nothing. A 1 GB swap file helps too, so MySQL doesn't get OOM-killed at the worst moment.
Your stack is fine as it is. A caching plugin is enough at a few hundred visits a day, and Cloudflare free in front takes a lot of the load off.
One thing I'd sort out from day one instead of later is backups. I back up with restic, encrypted with a passphrase, to a cheap storage box, and I have a cron job pinging healthchecks.io so I actually hear about it when the site goes down instead of finding out from a visitor. And test a restore once, I learned that one the hard way.
I would say 1GB is fine if you are willing to optimise a lot. Got sites running with similar specs and not too many visits and it's alright.
If you expect traffic to grow within reasonable time I'd get a slightly bigger box. Just to make sure you don't have to move or upgrade.
1 GB serves cached pages all day, it's the uncached stuff that bites you.. running a backup, updating plugins, or clicking around wp-admin while MariaDB is eating half the RAM.
Unless the price jump is steep, imo, I'd just start at 2 GB (plus a small swap file) so an update spike doesn't knock the database offline.
Use Hestia control panel as you will be able to optimise the web server for WordPress
If you just want wordpress, use a webhosting instead of a vps, Limitlesshost has really good prices (especially during sales) and uses softaculous for auto-updating. WP is a constant target, so you really want to ensure updates roll out as quickly as possible.
Thanks, that explains it well. Cached pages are fine, and the real risk is a backup or plugin update spiking memory while the database is running. I'll stay at 2 GB and add a small swap file. Is 1 to 2 GB of swap a reasonable size, and do you lower swappiness for MariaDB?
2GB ram, coupled with openlitespeed + lscache and cloudflare in front for static assets will be more than enough. Openlitespeed is enough if you really don't want to manually tweaks things. 1gb swap is enough for this.
1C2G is enough for a small WP site. I ran mine on 2C2G with 1Panel + nginx, fine. Add a cache plugin and you're good. Don't overthink the stack.
1GB RAM, and 1 CPU are enough for this kind of site. Even if you add some caching plugin and add another 200-300 posts/pages to the wordpress still it will work fine.
But if you are going to add more pages/plugins then go for 2GB RAM.
I've a WP site on shared account using 1CPU, 2GB RAM, have 5K pages, and daily traffic of about 3K users. Everything is cached. So working fine.
@Jannat_IT — on the swap question, 1 GB is plenty for this setup, and I would not go to 2 GB just for swap. With 2 GB RAM, swap is really just a safety net for those spikes nicenic mentioned — a backup or plugin update running while PHP-FPM is busy — not something MariaDB should be living in day to day. If the database starts swapping regularly, the fix is tuning, not more swap.
I set vm.swappiness to 10 on a similar 2 GB box, which keeps the kernel from pushing MariaDB's buffer pool out to disk too eagerly, and set innodb_buffer_pool_size to around 256-512 MB so MariaDB has a fixed, predictable footprint. Then keep PHP-FPM on ondemand with a low max_children — 3 or 4 for your traffic — so a traffic spike cannot spawn enough workers to eat the RAM MariaDB needs. With that combination, a 1 GB swap file has stayed almost untouched for me, and the one time it did get used was during an unattended update, which is exactly when you want it there instead of the OOM killer.
Hello there,
If you would like cPanel Hosting, we can help in Istanbul/Turkey location with our Wordpress Hosting plans.
https://tarisu.com/hosting/wordpress-hosting
Regards.
maybe try @NameBig current offer of web hosting in Singapore: https://lowendtalk.com/discussion/223619/namebig-bf-sale-singapore-web-hosting-68-off-recurring-nvme-free-cdn-lscache
look very yummy i dont have any need and still want to grab T_T
For a small WordPress site, 1-2 vCPU and 2GB RAM is plenty if you set it up sensibly. I'd go Nginx or OpenLiteSpeed with PHP-FPM 8.x, MariaDB with a trimmed innodb_buffer_pool_size (~256-512MB), and Redis object cache. Add a page cache plugin (or nginx fastcgi_cache) and most hits never touch PHP at all. Put 1-2GB of swap on it as a safety net, and put Cloudflare free in front for static assets. Also disable xmlrpc and limit login attempts, since bots hammer those more than real traffic.
Our web hosting is container-based, allowing for a wide range of uses, in fact some users have successfully installed Uptime Kuma on our platform and are utilising it effectively.
~Vikas