Solutions
Start from the workload, not the spec sheet.
What each common workload actually needs, which plans suit it, and the limitations worth knowing before you deploy.
- WebsitesMarketing sites, blogs and brochure sites spend most of their time idle and then need headroom for a traffic spike. The sizing below reflects that shape rather than a peak-load figure.Typical profile2 to 4 vCPU · 4 to 8 GB memory
- E-commerceA store is a database application with images attached. Sizing follows catalogue size, concurrent checkouts and how much history you keep, not the number of visitors.Typical profile4 to 8 vCPU · 8 to 16 GB memory
- Game serversPlayer experience is dominated by network distance and by the server keeping a steady tick rate. Both are addressed by choosing the right region and leaving headroom.Typical profile4 to 6 vCPU · 8 to 16 GB memory
- DevelopmentDevelopment machines are bursty: idle for long stretches, then fully loaded for a few minutes. Processor-heavy plans suit that pattern better than memory-heavy ones.Typical profile4 to 8 vCPU · 8 to 12 GB memory
- AutomationAutomation workloads are usually small and long-lived. The important choices are reliability of the schedule and where the machine sits relative to the services it talks to.Typical profile2 to 4 vCPU · 4 to 8 GB memory
- Remote desktopA remote desktop needs an appropriate image and an appropriate license. Both are choices you make in the configuration flow, and both affect the price.Typical profile4 vCPU · 8 GB and up memory
- DatabasesA self-managed database lives or dies by its working set fitting in memory and by its backups being restorable. Everything else is tuning.Typical profile4 to 6 vCPU · 16 to 32 GB memory