Creating Power Flexibility in Datacenters via Query Routing
Organizations: Carnegie Mellon University · Bosch Center for AI · Cornell University
Abstract
The growing energy requirements of large language model inference highlight the need for datacenters to support safe grid operation by providing power demand flexibility, while maintaining service for interactive workloads. This work investigates query routing as a mechanism to enable such capability by dynamically allocating queries across different language model instances without deferring requests. We develop a general analytical framework that connects query arrival rates and sequence length distributions to token iteration time, request residence time, serving capacity, and power consumption of model instances. Leveraging this framework, we characterize the feasible query routing allocations and the corresponding power demand flexibilities, enabling the selection of routing strategies to achieve desired power consumption behavior. We validate our framework across four GPU platforms on language models ranging from 1B to 70B parameters, obtaining 2.8% mean absolute percentage error in estimating achievable power flexibility. We evaluate our approach on a real trace-driven simulation of a 10,000 H100 GPUs datacenter, exhibiting flexibility up to 16% of total power consumption, with 90% of the desired power reduction achieved within approximately 10 seconds. These results establish query routing as an effective mechanism for datacenter power demand flexibility and demonstrate the broader applicability of our proposed framework to datacenter level planning and orchestration.
Figures & tables
| Domain | Application |
|---|---|
| Serving design | Model instance pool sizing, deployment comparisons, demand growth headroom. |
| Power Control | Feasible targets, sustained power curtailments, and transition planning. |
| Energy coordination | Joint inference/training budgets, storage support, and cost or carbon objectives. |
| Broader routing | Allocation across execution choices or locations, subject to eligibility constraints. |
Appendix figures & tables7 assets
Supplementary material from the paper’s appendix.
Appendix
| Notation | Description |
|---|---|
| Query arrival rate (requests/s) | |
| request concurrency | |
| maximum request concurrency | |
| Mean prompt and output lengths (tokens) | |
| number of prefill tokens in one chunk | |
| approximate token iterations per request |
| Quantity | H100 | RTX 5090 | RTX 8000 | V100 |
|---|---|---|---|---|
| Power consumption at concurrency , | 0.9 | 2.5 | 0.7 | 2.5 |
| Power consumption at query arrival rate , | 5.3 | 6.9 | 13.3 | 8.8 |
| Token iteration time, | 3.3 | 5.4 | 5.0 | 6.3 |
| Request residence time, | 5.5 | 6.2 | 11.1 | 10.5 |
| Request Throughput, | 5.6 | 6.7 | 13.5 | 9.0 |
| Request Concurrency, | 10.6 | 9.8 | 30.1 | 31.0 |
| Mean-power error (W) | Power std. dev. (W) | Response time (s) | ||||
|---|---|---|---|---|---|---|
| Controller | Median | 90th pct. | Median | 90th pct. | Median | 90th pct. |
| Analytical model, open loop | 34 | 131 | 27 | 136 | 6.5 | 16.5 |
| PID feedback | 14 | 85 | 108 | 194 | 12.0 | 18.6 |
| Program or Guideline | Response Requirement | Duration and Objectives |
| Grid services and demand response | ||
| ERCOT Fast Frequency Response ( ercot_operating_guide_2026 ) | Full response within 15 cycles (0.25 s at 60 Hz). | Sustain for 15 min or until recall, whichever occurs first. |
| ERCOT RRS, high-set under-frequency relay ( ercot_operating_guide_2026 ; ercot_protocols_2026 ) | Interrupt load within 30 cycles (0.5 s). | At least 1 h capability for this resource category following restoration instructions. |
| ERCOT Regulation ( ercot_protocols_2026 ) | Respond to control signals within 5 s; deliver capacity within 5 min. | At least 30 min duration capability with continuous signal tracking. |
| PJM Regulation ( pjm_manual12_2026 ; pjm_manual11_2026 ) | Respond immediately and reach bid capability within 5 min. | Half-hour commitments with continuous tracking and performance scoring. |
| ERCOT Emergency Response, ERS-10 ( ercot_protocols_2026 ) | Meet deployment obligations within 10 min of dispatch. | Sustain until recall. Cumulative obligations are 24 h in December–March contract periods and 12 h in other terms. |