Hardware requirements¶
Sizing comes from Residion’s Hardware Reference and Sizing specification (v0.9). User bands (~10–25 / ~100 / ~250) are design targets, not measured capacity.
Profiles¶
| Profile | CPU | Cores | RAM | Storage | Users (design target) |
|---|---|---|---|---|---|
| P0 — below floor | under floor | < 8 | < 32 GB | < 256 GB | install blocks |
| P1 — minimum | x86-64, no AMX | 8–15 | 32–48 GB | 256 GB SSD | ~10–25, degraded |
| P2 — recommended | AMX Xeon (4th-gen+) | 16–32 | 64–128 GB | 512 GB NVMe | ~100 |
| P3 — performance | AMX Xeon, tuned RAM | 32–56 | 128–256 GB | 1 TB+ NVMe | ~100–250 |
| P4 — multi-server | 2+ P2/P3 nodes | per node | per node | per node | 250+ |
P4 is not available
Profile P4 is designed, not built. Clustering is not implemented. Do not plan a multi-node deployment against current software.
Installer pre-check¶
The installer blocks hosts that are below:
- 8 cores
- 32 GB RAM
- 256 GB storage
- or lack AVX2
It warns on:
- non-AMX CPU (degraded P1 behaviour)
- 32–48 GB RAM
- 256–512 GB storage
- spinning disk
- a hypervisor that masks CPU features
Deployment modes¶
- Bare metal is the reference deployment.
- Virtualisation is supported only if the hypervisor passes through CPU features (AMX/AVX). Some hypervisors mask them by default, silently dropping a P2-class host to P1 behaviour.
GPU¶
A GPU is never required. When present it unlocks 32B-class interactive (~24 GB VRAM), vision-at-inference, and fine-tuning (batch). Without a GPU, multimodal degrades to the OCR-to-text CPU path and 32B-class work is batch-only.
How to verify¶
- Confirm core / RAM / storage / AVX2 against the pre-check floor above.
- If virtualised, confirm AMX/AVX pass-through with your hypervisor documentation before expecting P2/P3 behaviour.
- After install, open Operator Console → Deployment and confirm the reported status matches the host you provisioned. See Deployment.
If it fails¶
| Symptom | Likely cause | Action |
|---|---|---|
| Installer refuses to proceed | Below P0 floor or missing AVX2 | Resize the host; do not attempt to bypass the pre-check |
| Unexpectedly slow / degraded | Hypervisor masking AMX/AVX, or P1-class hardware | Verify CPU feature pass-through; accept P1 design target or move to P2+ |
| Looking for a second node | Expecting P4 | Not available — stay on a single host |