Distribute CPU, RAM and Storage
Arbit between a large VM or several small ones: good sizing practices in your envelope.
Ready to start your service? Check offers and order online.
View offers and orderDivide CPU, RAM and storage between multiple VMs
The VPS Reseller's interest is to compose your architecture in a single envelope. Here's how to arbitrate effectively.
Current scenarios
- 1 monolithic VM, simple, everything on a machine (small project, lab)
- 2 VM prod + test, isolating the production updates
- 3 VM web + BDD + bastion, role separation and network hardening
- N VM light, reseller customers, one VPS per end customer
Sizing rules
- Do not over-allocate vCPU: 2-4 vCPU is often enough for a modest website
- Plan RAM for MySQL/Redis (minimum 2 GB for light BDD)
- Disc: OS + logs + data; 20-30% margin forecast
- 1 IPv4 per exposed VM; internal VM can share via NAT if your architecture allows
Start small, measure the load, and then create an additional VM rather than oversize from the start.
Examples of architecture: prod / test / services