Usage and limits
Your Lane’s caps
Section titled “Your Lane’s caps”Your admin sets four caps for your Lane: RAM, disk, the number of machines and CPU cores. af whoami --json and af usage --json show yours.
Need more? Ask your admin; they can raise any cap.
af whoami --json # your Lane and its limitsaf usage --json # caps against what you use, per machine (never anyone else's)How machines count
Section titled “How machines count”- Every machine counts against RAM, disk and machines, running or stopped. A stopped machine frees the platform’s CPU and RAM, but not your caps. Delete what you no longer need.
- A Runner’s 50 GB cache disk counts against your disk cap while it exists.
- Cores. Your Lane owns a number of physical cores. Each core is two vCPUs, and a machine’s cores are its own: two machines never share one. A size S Box needs 2 cores, M needs 4 and L needs 6. Asking for more cores than your Lane has free is
LANE_LIMIT. CI-size Runners are the exception: they share your Lane’s CPUs and hold no core. box create,box resizeandrunner createin your Lane run one at a time, so no two pick the same cores. A call waits its turn and says so;--timeoutdoes not count that wait.
When you hit a limit
Section titled “When you hit a limit”| Code | Means | Do |
|---|---|---|
LANE_LIMIT |
Your Lane’s cap would be passed | Delete something (a stopped machine still counts), use a smaller size, or ask your admin to raise the cap |
HOST_FULL |
The platform as a whole has no room right now | Wait retryAfterSeconds once, or use a smaller size, or try later. Never loop |
Before starting a machine, af asks the platform how much memory is free for new starts. The answer is one number, and it never tells you who uses the rest.