Hardware Sizing¶
Sizing depends on request rate, TLS usage, body inspection size, WAF rule count, logging volume, and retention requirements.
| Size | Use case | CPU | Memory | Disk |
|---|---|---|---|---|
| Small | Low traffic websites and evaluation | 2-4 vCPU | 4-8 GB | 20-50 GB |
| Medium | Production apps/APIs | 8 vCPU | 16 GB | 100 GB |
| Large | High traffic / multiple apps | 16 vCPU | 32 GB | 250 GB |
| XL | Enterprise / multi-site | 32+ vCPU | 64+ GB | 500 GB+ |
Capacity factors¶
- TLS handshakes and cipher choices.
- Request body inspection size.
- Number and complexity of WAF regex rules.
- Log volume and local retention.
- Rate-limit cardinality.
- Number of backend pools and health checks.
Best practice¶
Keep at least 20-30% spare CPU and memory under expected peak load. Use a load balancer and multiple Core nodes for production HA.