Utilization
How much of the cluster’s capacity turns into delivered compute, and how much of it is idle or unavailable.
Data freshness unknown
Utilization (of available)
not yetYear to date. Excludes hours when hardware was down or in maintenance.
Utilization (of installed)
not yetYear to date, against every GPU-hour on the floor including downtime.
Availability
not yetShare of installed GPU-hours that were up and schedulable.
GPU-hours delivered
not yetYear to date.
Allocated, not measured
These figures describe GPU-hours allocated by the scheduler. Slurm
knows a GPU was assigned to a job; it does not know whether that GPU was
busy. Per-device utilization requires DCGM exporters, which are not yet
deployed — see Methodology.
Nothing on this site claims measured device utilization until they are.
Capacity over time
GPU-hours per day
Stacked to total installed capacity: what was allocated, what sat idle, and what was unavailable.
Utilization and availability rates
Where the hours go
By GPU model
Demand is rarely uniform across generations — this is the chart that tells you which hardware to buy next.
By partition
By quality of service
The cluster runs three QoS tiers — general,
protected, and interactive. Preemptible work
running in gaps is capacity that would otherwise have been wasted.
Usage by hour and weekday
Mean GPU-hours allocated, last 90 days.