Overview
ALYPOD offers several CPU Pod families. Picking the right one keeps performance predictable and your bill low. This article helps you match a workload to a Pod type before you deploy in the ALYPOD Console.
Pod families at a glance
- Shared CPU Pods — vCPU shared with other tenants. Best for web hosting, blogs, staging environments and light application servers.
- Dedicated CPU Pods — vCPU reserved for you. Choose these for databases, game servers, CI/CD runners and anything with sustained CPU load.
- NVMe Disk Pods — high-IOPS NVMe storage. Ideal for PostgreSQL, MySQL and other I/O-heavy services.
- Windows Pods — Windows Server with RDP. Use for .NET, MSSQL or Windows-only tools.
- ARM aarch64 CPU Pods — native Arm servers. Good for container hosts and workloads that ship Arm images.
How to size a Pod
- Estimate baseline CPU: pick dedicated vCPU if you expect sustained load above roughly half of one core.
- Estimate RAM: reserve at least 1 GB for the OS, then add your application's needs.
- Estimate disk: start with NVMe if the workload is database or IO heavy; otherwise the standard disk is usually sufficient.
- Add a backup or a Storage Box if the data is important.
Most Pods can be resized later, but resizing usually requires a reboot and may change disk layout, so it is worth getting roughly right first.
Troubleshooting
- Problem: The app feels slow on a Shared Pod. Solution: Move to a Dedicated CPU
Pod if CPU steal is high (check with
top). - Problem: Disk latency is high. Solution: Migrate to an NVMe Disk Pod.
Related articles
- [Deploying your first Pod]
- [Supported operating systems overview]
- [Upgrading or downgrading a service]
