2–4 GB
Often suitable for light development, small applications or modest sites when the software stack is efficient.
VPS sizing guide
Size VPS memory from the workload—and leave deliberate headroom.
There is no reliable visitor-to-RAM formula. Application design, database behaviour, caching, concurrency and operating-system services all matter.
Make an evidence-led choice
Start with components, then measure
Memory must cover the operating system, web server, runtime, database, cache, control panel, security tools and workload peaks. A small static site can use far less than a dynamic store or container platform. Repeated swapping, out-of-memory events or killed services indicate that memory or configuration needs attention.
8 GB
A common starting point for busier dynamic sites, moderate databases or several lightweight services.
16 GB and above
Consider for larger databases, multiple containers, heavier concurrency or memory-intensive workloads.
Checklist
A defensible sizing method
- Measure peak resident memory on the existing environment.
- Add the destination operating system and management overhead.
- Allow headroom for deploys, backups, traffic spikes and cache growth.
- Monitor swap, OOM events, latency and database buffers after launch.
- Scale from evidence rather than paying indefinitely for unused capacity.
Before you order
Confirm the service boundary.
Plan names do not guarantee management, backups, migration or application support. Review the published specification and terms, and ask HostUrServer about any workload-specific requirement before purchase.
Discuss the workload →Next step