A rack is only useful if the whole site can support its workload.
Place devices within racks, rooms, buildings and plot with sourced assumptions.
Tagged equipment and site assumptions.
One explicit revised equipment assumption; preserve the original baseline.
Place devices within racks, rooms, buildings and plot with sourced assumptions.
Fit, aisle, mass, floor load and site assumptions.
Original configuration and changed input remain identifiable.
Physical fit and site assumptions retain their source and units.
Keep distinct power bases and propagate losses, heat and cooling demand.
Equipment/power assumptions with containment context.
Keep distinct power bases and propagate losses, heat and cooling demand.
Nameplate, provisioned peak and utilization basis.
IT heat, conversion losses and facility demand.
Nameplate, provisioned peak and utilization are different power bases.
Derive memory and throughput bounds from the workload and selected equipment.
Selected capacity and placement.
Model shape, precision, context and concurrency.
Derive memory and throughput bounds from the workload and selected equipment.
Weights, workspace, KV memory, precision and concurrency.
Compute/memory bounds and selected utilization assumptions.
An infeasible memory requirement prevents an operating-energy result for that configuration.
Balance load, supply, storage and grid under the selected time basis.
Calculated facility load under the selected power basis.
Duration/weather/supply/storage assumptions.
Balance load, supply, storage and grid under the selected time basis.
Load, generation, exchange, shortfall and storage state.
Base/low/high inputs and their source quality.
Time-based supply and storage remain balanced, including shortfall.
Join physical and workload results and expose the binding constraint.
Electrical and thermal feasibility.
Memory feasibility and workload bounds.
Calculation with its time basis, not an observed operating result.
Join physical and workload results and expose the binding constraint.
Feasible, failed and unresolved results.
Units, method, input lineage and comparison basis.
Calculated feasibility is an illustrative evaluation, not commissioned hardware performance.
Tagged equipment and site assumptions.
One explicit revised equipment assumption; preserve the original baseline.
Place devices within racks, rooms, buildings and plot with sourced assumptions.
Fit, aisle, mass, floor load and site assumptions.
Original configuration and changed input remain identifiable.
Physical fit and site assumptions retain their source and units.
Equipment/power assumptions with containment context.
Keep distinct power bases and propagate losses, heat and cooling demand.
Nameplate, provisioned peak and utilization basis.
IT heat, conversion losses and facility demand.
Nameplate, provisioned peak and utilization are different power bases.
Selected capacity and placement.
Model shape, precision, context and concurrency.
Derive memory and throughput bounds from the workload and selected equipment.
Weights, workspace, KV memory, precision and concurrency.
Compute/memory bounds and selected utilization assumptions.
An infeasible memory requirement prevents an operating-energy result for that configuration.
Calculated facility load under the selected power basis.
Duration/weather/supply/storage assumptions.
Balance load, supply, storage and grid under the selected time basis.
Load, generation, exchange, shortfall and storage state.
Base/low/high inputs and their source quality.
Time-based supply and storage remain balanced, including shortfall.
Electrical and thermal feasibility.
Memory feasibility and workload bounds.
Calculation with its time basis, not an observed operating result.
Join physical and workload results and expose the binding constraint.
Feasible, failed and unresolved results.
Units, method, input lineage and comparison basis.
Calculated feasibility is an illustrative evaluation, not commissioned hardware performance.
An illustrative design calculation under explicit equipment and workload assumptions.
Additional mechanisms are described in the technical reference.
A proposed compute-site scenario showing the relationship between equipment, energy and inference.
A planner assembles devices into racks and checks fit, clearance and floor loading in the intended room.
Component demand, PSU losses, redundancy and cooling contribute to facility requirements. The calculation keeps its distinct power bases.
Model weights and KV cache must fit the proposed memory and placement. Batch, concurrency and compute bounds determine the scenario’s service limits.
Model weights and KV cache must fit the proposed memory and placement. Batch, concurrency and compute bounds determine the scenario’s service limits.
An hourly energy scenario adds grid limits, generation and storage assumptions. The planner compares alternatives with the same inputs and opens the methods behind the limiting factor.
The product page explains its specific mechanisms and operating scope.
Connected systemThe product page explains its specific mechanisms and operating scope.
Connected systemThe product page explains its specific mechanisms and operating scope.
What could these mechanisms make possible for you?
Discuss a capacity scenario