Recommended Free Tools
There is no universal VPS size. The right plan depends on what the server runs, how many people use it at once, and how much headroom you want for spikes. Start with your software, pick a plan that fits it, then watch real CPU and memory behavior and resize when pressure is sustained. Memory is usually the first limit to bite on a small server, but vCPU count alone also tells you little about CPU performance.
No independent, industry-wide “typical VPS” benchmark exists in the official provider material, so this guide doesn’t invent one. The concrete figures below come from Amazon Lightsail’s WordPress documentation and are labeled as such.
As an Amazon Associate I earn from qualifying purchases.
Start with the workload, not the plan list
Four things set your starting size:
- The application stack: a static site, a WordPress install, a database server and a build runner all behave differently.
- The database: AWS notes that WordPress plugins, themes and the database can consume significant memory.
- Extensions and background services: plugins, queues, cron jobs, and anything else that runs alongside the main app.
- Concurrency: how many requests or jobs overlap, not total monthly visitors.
Leave room for the operating system and normal spikes. A plan that fits your workload only when idle is too small.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Worked examples
Small WordPress site
Amazon Lightsail’s WordPress guidance describes 512 MB–1 GB of RAM as suitable for a small, low-traffic site with minimal plugins. The same documentation cautions that plans this small are more likely to hit memory pressure. Treat it as a starting category, not a guarantee. The publication date of that page was not stated in the version reviewed.
#1 Best Overall
WordPress with page builders, WooCommerce or many plugins
AWS recommends 2 GB of RAM and up for Lightsail WordPress sites using page builders such as Elementor or Divi, WooCommerce, or many active plugins. Traffic, caching, theme and plugin quality, and database load can still push the real requirement higher or lower. These are AWS’s recommendations for its own WordPress configuration, not universal VPS rules.
Sustained CPU-heavy work
DigitalOcean describes its CPU-optimized Droplets as suited to sustained CPU-demanding tasks such as CI/CD, video encoding, machine learning, batch processing and front-end web servers. It also offers general-purpose and memory-optimized families. The lesson is to buy for the resource that is actually constrained: a database cache wants memory, an encoder wants CPU, and the two don’t scale in the same ratio.
Bursty CPU work
Some plans, including Lightsail’s, define a CPU baseline plus accrued burst capacity. That suits intermittent peaks, such as a quiet site with occasional traffic surges, but differs from a workload that needs high CPU continuously. Check the baseline and burst rules for the exact plan you’re considering, since these values are provider-specific and change.
Why vCPU count isn’t enough
Two plans with the same vCPU count can perform differently. Ask whether the CPU is shared or dedicated, whether the plan is burstable or sustained, and what the baseline is. Metrics can also mislead: AWS explains that its Lightsail CPU graph averages utilization and baseline for instances with multiple vCPUs, so read the graph against the provider’s definition.
Rank #3
- HP MicroServer Gen10 Plus Tower Server for Business with Microsoft Windows Server 2019 OS!
- Intel Xeon E-2224 Quad-Core 3.4GHz 8MB CPU, Up To 4.6GHz Turbo
- 32GB (2 x 16GB) DDR4 PC4-21300 2666MHz Unbuffered Memory
- 16TB (4 x 4TB) 7.2K 6Gb/s SATA 3.5" HDDs in RAID
- Hard drives and memory upgrades included separately NOT installed, installation required.
Cut demand before buying more
Caching can lower both CPU and memory use by avoiding repeated PHP execution and database queries. AWS lists page caching, object caching and a CDN as options for WordPress. Try these before assuming you need a bigger plan, though AWS is also direct that “the most effective way to improve WordPress performance is to run on an instance bundle with enough memory for your workload.”
How do I know if my server is running out of memory?
Typical symptoms, per AWS’s Lightsail guidance: slow page loads, timeouts under modest traffic, and database connection errors (often because the database process was killed).
Rank #4
- Run
free -mand look at theavailablecolumn, not “free”. Available includes memory the kernel can reclaim from cache. - Check kernel messages for out-of-memory kills, for example with
dmesgorjournalctl -k, and search for “Out of memory” or “Killed process”. - Repeat during a busy period, since an idle reading proves little.
AWS’s Lightsail troubleshooting page says: “If available is below 50 MB, your instance is under heavy memory pressure and is at risk of OOM-killing processes.” That threshold is AWS’s guidance for Lightsail; don’t treat it as a rule for every Linux VPS, especially larger ones where 50 MB would be a tiny share of memory.
If you use Lightsail’s newer WordPress blueprint, AWS also addresses whether automatic memory tuning is already applied. Don’t assume that tuning exists on a WordPress install built any other way.
Best Value
What to monitor before resizing
- Memory and CPU over representative busy periods, not just averages.
- Disk and bandwidth, since plans bundle storage and transfer alongside compute.
- Failures: killed processes and user-visible slowdowns are stronger evidence than a brief spike.
A single short spike rarely justifies a bigger plan. Recurring pressure does.
Comparing plans on the right axes
| Axis | What to ask |
|---|---|
| Memory capacity | Is there room for the OS, application processes and database at expected concurrency? |
| CPU allocation | Shared or dedicated? Burstable or sustained? What baseline and burst limits apply? |
| RAM-to-vCPU balance | DigitalOcean’s Droplet families use different ratios for different workloads; match the family to your bottleneck. |
| Storage and transfer | AWS describes Lightsail bundles as RAM, vCPUs, SSD storage and a transfer allowance together. |
| Resize path | Can you change size without rebuilding? What happens to disk, downtime and backups? |
| Price and region | Both change often; check the live price in the region you will actually deploy to. |
Resizing safely
Procedures differ by provider. On Lightsail, AWS documents creating a snapshot and launching a larger instance from it. DigitalOcean’s Droplet resize documentation says resizing can increase CPU and RAM, and that depending on the option you choose, disk size may increase permanently, which can limit your ability to scale back down. Before touching a production server, take a backup or snapshot, plan for downtime, and read your provider’s current instructions for rollback.
The Bottom Line
Pick a starting plan from your actual stack, using provider guidance such as AWS’s 512 MB–1 GB for minimal WordPress and 2 GB and up for heavier builds as examples only. Then measure available memory and sustained CPU under real load, add caching, and resize when pressure recurs.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
