Resource Limits
Every app on Zerokie runs with resource limits to ensure isolation and predictable performance. You can customize these limits to match your workload.
Default limits
Section titled “Default limits”If you do not specify limits, apps are created with:
| Resource | Default |
|---|---|
| CPU | 256 MHz |
| Memory | 512 MB |
Setting custom limits
Section titled “Setting custom limits”Use the --cpu and --memory flags when creating an app:
zerokie apps create \ --name my-api \ --image my-registry.com/my-api:latest \ --port 3000 \ --cpu 512 \ --memory 1024--cpusets the CPU limit in MHz.--memorysets the memory limit in MB.
Choosing the right limits
Section titled “Choosing the right limits”| Workload | Recommended CPU | Recommended Memory |
|---|---|---|
| Static site / proxy | 256 MHz | 256 MB |
| Node.js API | 512 MHz | 512 MB |
| Java / .NET service | 512-1000 MHz | 1024 MB |
| Data processing | 1000 MHz | 2048 MB |
Start with the defaults and increase if your app shows signs of resource pressure (slow responses, OOM kills).
What happens at the limit
Section titled “What happens at the limit”- CPU: Your app is throttled when it exceeds the CPU allocation. It continues running but responds more slowly.
- Memory: If your app exceeds its memory limit, the container is killed and restarted automatically.
Next steps
Section titled “Next steps”- Pass configuration values with environment variables.
- See the full CLI Reference for all available flags.