What happened
NVIDIA introduced DSX MaxLPS, a site-level system combining dynamic power allocation, workload-specific GPU tuning and 45 °C liquid-cooling design. Its Dynamic Power Software is in Developer Preview and is intended to redistribute unused power across managed racks and GPUs.
On Aug. 21, 2026, NVIDIA published a technical blog introducing DSX MaxLPS, which it expands as Maximum Land Power Shell. The term refers to the three fixed constraints that shape an AI factory: land, utility power and the physical building that contains power distribution, cooling, networking and compute equipment. NVIDIA presents MaxLPS as a combination of dynamic power allocation, software techniques for improving output at a fixed power level, and site design based on 45 °C liquid-cooling inlet operation. The company describes the system as a way to increase throughput within an existing facility envelope, rather than as a way to increase the site's total power supply.
NVIDIA's Dynamic Power Software is currently in Developer Preview. According to the source, it models the data-center hierarchy from the utility connection to groups, racks, nodes and GPUs. Operators set power budgets, resource groups and policies; the software then compares allocated power with actual consumption and makes unused headroom available to other equipment within the same managed group. It also collects power telemetry and can respond to site-level events, maintenance conditions or emergency policies on a best-effort basis. NVIDIA says DSX Exchange, an open-source event bus that is also in Developer Preview, can connect the power software with building-management systems, electrical monitoring, cooling infrastructure, grid interfaces and compute schedulers, but says that exchange layer is not required for MaxLPS to function.
The source illustrates the problem with two examples. In a 100 MW power-budget waterfall, NVIDIA assigns 20 MW to facility overhead, 10 MW to rack losses and 10 MW to operational inefficiencies involving failures, restarts and checkpointing, leaving 60 MW for AI load. It separately describes a 540 kW site budget in which static provisioning strands 170 kW and dynamic provisioning enables another rack. These are presented as illustrative figures, not as measurements from a named operating data center. NVIDIA also reports representative inference evaluations in which provisioned rack power fell from 125 kW to 90 kW on GB200 NVL72 and from 136 kW to 101 kW on Vera Rubin NVL72. It says those changes preserved workload throughput, enabled 39% and 35% more racks respectively, and improved performance per watt by about 1.5 times and 1.3 to 1.4 times. The tested workloads were DeepSeek-R1 and Kimi-K2.5. The supplied source does not provide independent validation or full test protocols.
Read the primary source: developer.nvidia.com ↗
Why it matters
AI data centers are increasingly constrained by electricity, cooling and physical infrastructure. If NVIDIA's claims hold in independent deployments, the system could increase useful AI output from existing power connections, but the source does not establish the costs, reliability or broader efficiency of the approach.
Electricity is becoming a direct constraint on the expansion of AI infrastructure. A data center can have land, network equipment and rack space available while still being unable to energize more GPUs because its utility connection, distribution equipment or cooling plant has reached its design limit. NVIDIA's proposal targets a specific inefficiency in that arrangement: racks are often provisioned for peak demand even though workloads move through phases such as compute bursts, memory-bound execution, synchronization, checkpointing, prefill and decode. If power can be safely shifted during those changes, a facility might produce more useful inference or training output without immediately securing another power connection.
The approach also shows why this is a facilities project rather than a software-only optimization. NVIDIA says sites should be designed around a fixed gross power envelope, then sized for power distribution, cooling, networking and rack positions that can support the intended long-term GPU count. The company recommends planning for 45 °C direct-liquid-cooling inlet operation for Vera Rubin NVL72 systems. Warmer coolant can allow dry coolers or other forms of free cooling to handle more of the annual heat-rejection load, reducing reliance on mechanical chillers in suitable climates. That potential depends on local weather, equipment sizing, redundancy and controls. Facilities that were not designed for the relevant temperatures, liquid loops or power flexibility may not be able to capture the claimed gains without significant retrofit work.
For operators, the practical attraction is optionality. A site could initially populate fewer racks while training-heavy workloads draw more power, then add hardware later if the workload mix shifts toward inference and average rack demand falls. That could change the timing of capital spending and facility expansion. It does not, by itself, reduce total electricity demand from AI or prove that fewer data centers will be built. More capacity inside an existing envelope could instead make additional AI services economically viable. The source names no customers, deployment scale, acquisition cost, measured annual energy savings, water consumption, failure rate or service-level impact. Its central capacity and performance claims remain NVIDIA claims based on representative evaluations.
What to watch next
The key tests are whether Dynamic Power Software reaches general availability, whether independent operators reproduce the reported gains, and how the system behaves under failures, changing workloads and extreme weather. The required thermal and electrical design may limit adoption in existing facilities.
The first question is product maturity. Dynamic Power Software and DSX Exchange are both identified as Developer Preview, so their supported hardware, interfaces, operational guarantees and production availability remain unknown. Future documentation should clarify how policies are enforced, how quickly power can be redistributed, what happens when telemetry is delayed or wrong, and whether emergency actions are deterministic. NVIDIA says the control loop operates on a best-effort basis during power events, an important limitation for facilities that must maintain strict redundancy and service commitments. It will also matter whether the system can work with equipment and schedulers outside NVIDIA's own stack.
The second question is reproducibility. A useful comparison would publish the unmanaged static baseline, workload configuration, number of runs, throughput definition, latency, service error rate, GPU utilization and power-measurement boundaries. NVIDIA itself lists throughput, latency, service error rate, power draw, utilization and policy compliance as metrics for a scoped validation, but the supplied source does not provide those results in full. Independent testing across inference, training and post-training workloads would show whether the reported improvements generalize beyond the two representative inference cases. Results should also be separated from gains caused by newer hardware, software versions, network changes or workload-specific tuning.
The third question is physical deployment. Operators will need evidence from sites with different climates, cooling architectures, utility constraints and reliability requirements. The 45 °C design may reduce chiller use in some locations but could require new heat-rejection equipment, controls or maintenance practices in others. Observers should track whether facilities can add the promised rack positions without expanding electrical distribution, cooling capacity or network infrastructure, and whether the system maintains throughput during hot weather, failures, restarts and checkpointing. Until those results are available, MaxLPS is best understood as a vendor-described infrastructure strategy and preview software, not an independently established industry-wide efficiency benchmark.
