Limitations
Nexaa’s serverless containers are designed to provide flexibility, scalability, and performance for containerized applications. However, to ensure reliability and efficiency across all tenants, the platform enforces a number of resource constraints. This page outlines the current limitations for CPU, memory, and networking.
Resource Limits Overview
| Resource | Limit | Scope |
|---|---|---|
| Namespace vCPU | Minimum: 1 vCPU Maximum: 12 vCPU Increment: 1 vCPU |
Namespace |
| Namespace Memory | Minimum: 2 GiB Maximum: 48 GiB Increment: 2 GiB |
Namespace |
| vCPU/Memory Ratio | Minimum: 1 vCPU to 2 GiB Maximum: 1 vCPU to 4 GiB |
Namespace |
| Container vCPU | Minimum: 0.25 vCPU Maximum: 12 vCPU Increment under 1 vCPU: 0.25 Increment above 1 vCPU: 1 vCPU |
Per Container |
| Container Memory | Minimum: 0.5 GiB Maximum: 16 GiB Increment under 1 GiB: 0.5 GiB Increment above 1 GiB: 1 GiB |
Per Container |
| Ingress Traffic | Only HTTP and HTTPS accepted | Per Container |
| Ephemeral Storage | A container has 10GB of internal storage | Per Container |
| Persistent Storage | Minimum: 1GB Maximum: 100GB |
Per Volume |
Notes
-
Container Resource Granularity:
Under 1 vCPU or 1 GiB memory, resource increments are smaller to support lightweight workloads. Beyond these thresholds, resources are allocated in whole units for performance consistency. -
Ingress Traffic:
Only HTTP and HTTPS ingress protocols are supported. Other protocols (e.g., TCP, UDP, WebSocket) are not currently supported. -
Ephemeral Storage: A container has 10GB of Ephemeral Storage. Which is deleted whenever a container is stopped. Use persistent storage for important data.
Increasing Limits
Some of the resource limitations described above can be increased on request.
Please contact support if you need more capacity for your namespace or specific container configurations.