18 lines
1.1 KiB
Markdown
18 lines
1.1 KiB
Markdown
# GPU Leases
|
|
|
|
`serving_gpu_leases` is the database coordination boundary for GPU capacity. A lease binds the
|
|
request, deployment, node and accelerator to reserved bytes, priority, owner, server-created
|
|
timestamps and an expiry. States are pending, granted, active, releasing, released, expired and
|
|
failed.
|
|
|
|
The scheduler locks the accelerator row before accounting and granting. This prevents two control
|
|
plane processes from independently spending the same capacity. Production and interactive are
|
|
serving priorities; background and benchmark remain defined but cannot pre-empt production in M5.
|
|
Expired leases are reaped and their unfinished request is failed with `LEASE_TIMEOUT`.
|
|
|
|
M10 distinguishes the lease purpose (`RESIDENCY_RESERVATION`, `REQUEST_EXECUTION`, or
|
|
`LOAD_TRANSITION`), records priority, expiry and a 64-bit worker generation, and subtracts only the
|
|
unmaterialized portion from physical headroom. Startup reconciliation expires orphan reservations,
|
|
preserves exact worker-reported residency and prevents duplicate adoption. The accelerator row lock
|
|
remains authoritative when two heavy admissions race.
|