Overview
Shared CPU Pods are ALYPOD's most affordable compute product. Your Pod runs on a physical host where CPU time is shared fairly between neighbouring Pods, while RAM, NVMe disk and your IP address stay fully dedicated to you. This article explains how sharing works so you can decide whether it fits your workload.
How sharing works
- CPU: you are guaranteed a fair share of the host's cores. Idle neighbours are not wasted — your Pod can burst above its baseline when the host has spare capacity.
- RAM: never shared. The full amount you order is reserved for your Pod.
- Disk: dedicated NVMe storage, not pooled.
- Network: a dedicated IPv4/IPv6 address and a committed bandwidth allowance.
Because CPU is shared, performance can vary slightly depending on what neighbours are doing. For steady low-traffic websites, mail servers, development boxes, CI runners and small databases this is rarely noticeable.
When to choose Shared CPU
- Personal and small-business websites.
- Staging and development environments.
- Lightweight daemons, VPN endpoints and monitoring tools.
- Workloads that burst occasionally and idle the rest of the time.
Choose a Dedicated CPU Pod instead if you need consistent single-core performance around the clock, for example busy databases, game servers or streaming transcodes.
Managing your Pod
- Sign in to the ALYPOD Console at account.alypod.com.
- Open Services and select your Shared CPU Pod.
- Use the Overview tab to view live CPU, RAM and disk graphs.
- Adjust resources at any time from Resize, or power actions from the console.
Troubleshooting
- Problem: CPU graph shows frequent saturation. Solution: check for runaway
processes with
toporhtop, then consider upgrading to a Dedicated CPU Pod. - Problem: Pod feels slow at peak hours. Solution: this is normal CPU contention; move time-sensitive workloads to a Dedicated CPU Pod.
Related articles
- [Dedicated CPU Pods explained]
- [How to deploy a CPU Pod]
- [Resizing a Pod (upgrading resources)]
