Start small
Use small sizes for:- Prototypes.
- Staging environments.
- Background jobs.
- Low-traffic APIs.
- Game server testing.
Scale up
Move to larger sizes when:- CPU stays high for long periods.
- The application is memory constrained.
- Disk usage is growing quickly.
- Network transfer increases.
- The VM is running multiple services.
Sizing guide
| Workload | Suggested starting point |
|---|---|
| Static site or small API | Small shared CPU plan |
| Worker or bot | Small shared CPU plan |
| Production web app | Balanced CPU and memory |
| Database on a VM | Prefer managed PostgreSQL first |
| Game server | Start small, upgrade when player count grows |
| CI runner | Match CPU and memory to workflow size |