Container Sizes
The following table provides a side-by-side comparison of resources and process limits applied to each container size, allowing for a clear overview of the capabilities and isolation characteristics associated with each profile.
| Size | Memory (MB) | Swap (MB) | CPU Priority | PID | FD |
|---|---|---|---|---|---|
| S | 256 | 64 | Low | 128 | 1048576 |
| M | 512 | 128 | Standard | 256 | 1048576 |
| L | 1024 | 256 | Standard | 512 | 1048576 |
| XL | 2048 | 512 | High | 1024 | 1048576 |
| 2XL | 4096 | 1024 | High | 2048 | 1048576 |
| 3XL | 8192 | 2048 | High | 4096 | 1048576 |
The default container size is M.
Prices are available on the Scalingo pricing page.
- CPU Priority
- All containers can use all available CPU cores.
- A High priority container receives twice the CPU share of a Standard priority container when CPU resources are contested.
- Following the same logic, a Low priority container receives half the CPU share of a Standard priority container when CPU resources are contested.
For example, if three containers are fully utilizing the CPU — one with High priority and two with Standard priority — the High priority container would receive 50% of the total CPU time, while each Standard priority container would receive 25%.
- PID
- Maximum number of processes the container can spawn.
-
FD (
nofile) - Maximum number of file descriptors a process can open.
Local Ephemeral Disk
Each container has a local ephemeral disk. Its content is lost when the container is restarted or redeployed. The performance of this disk depends on the container size and increases with larger sizes. See File System and File Storage for more information.