Dissecting the Carbon-SLO Tension in Geo-Distributed LLM Serving
summary
The gist
The gist Large Language Model (LLM) inference is driving a growing share of datacenter carbon emissions, and this paper addresses how to reduce these emissions by designing and evaluating
In short
The paper designed a latency-centric simulator and schedulers to reduce carbon emissions from geo-distributed LLM serving. It models continuous batching, queueing delays, and energy consumption across regions. The resulting MILP scheduler found a balance, achieving up to 60% carbon reduction while maintaining an average SLO violation of only 3%.
Key concepts
- Continuous Batching Behavior
- This describes how LLM inference handles requests by grouping them into a batch that is processed iteratively. The simulation models this by tracking the time taken for prefill steps and decode steps, showing how queueing delays depend on the current batch size and memory availability.
- Geo-distributed Serving Simulator
- This is a high-fidelity model simulating multiple datacenters spread across regions. It tracks network latency between regions, GPU engine states (like active batch load), and grid carbon intensity to accurately predict inference latency and energy use for scheduling decisions.
- Carbon-SLO Frontier
- This refers to the trade-off point where schedulers optimize both minimizing carbon emissions and meeting service level objectives (SLOs). The authors characterized this frontier, showing that a sophisticated optimization method can achieve significant carbon savings while keeping latency violations low.
- MILP Scheduler
- A Mixed-Integer Linear Programming model used to find the optimal scheduling policy. This scheduler uses the simulator's state information (load, queue depth) and grid data to make decisions that simultaneously optimize for both latency constraints and carbon reduction across the distributed system.
Terminology used across episodes
This episode discusses
- Dissecting the Carbon-SLO Tension in Geo-Distributed LLM Serving · Paper Radio
- Working with AI: Measuring the Applicability of Generative AI to Occupations
- LLMs as Research Tools: A Large Scale Survey of Researchers' Usage and Perceptions
- Artificial Intelligence Index Report 2025
- Chain-of-Thought Prompting Elicits Reasoning in Large Language Models
- Self-Consistency Improves Chain of Thought Reasoning in Language Models
- ReAct: Synergizing Reasoning and Acting in Language Models
- AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversation
- Sustainable AI: Environmental Implications, Challenges and Opportunities
- Learning-Augmented Competitive Algorithms for Spatiotemporal Online Allocation with Deadline Constraints
- Green-LLM: Optimal Workload Allocation for Environmentally-Aware Distributed Inference
- FREESH: Fair, Resource- and Energy-Efficient Scheduling for LLM Serving on Heterogeneous GPUs
- Routing LLM Inference to the Cleanest Grid in Real Time
- Splitwise: Efficient generative LLM inference using phase splitting
- DistServe: Disaggregating Prefill and Decoding for Goodput-optimized Large Language Model Serving
- SkyWalker: A Locality-Aware Cross-Region Load Balancer for LLM Inference
- Parallelization Strategies for Dense LLM Deployment: Navigating Through Application-Specific Tradeoffs and Bottlenecks
- The Llama 3 Herd of Models · Paper Radio
- Qwen2.5 Technical Report
- Mixtral of Experts
- Evaluating Large Language Models Trained on Code
The paper
Dissecting the Carbon-SLO Tension in Geo-Distributed LLM Serving · Read on arXiv
Burak Topcu, Musa Cim, Zuhal Ozturk, Mahmut Taylan Kandemir
The Pennsylvania State University
Transcript
Introduction to the show: ident: AI Radio. Generated commentary on the latest Artificial Intelligence papers.
Tom: I'm Tom.
Jane: And I'm Jane, here with Lu, Meng and our in-house large language model, Lalam.
Tom: Today's paper: "Dissecting the Carbon-SLO Tension in Geo-Distributed LLM Serving".
Jane: The gist Large Language Model (LLM) inference is driving a growing share of datacenter carbon emissions,
Tom: First, who's behind it and why it matters.
Paper summary: Tom: So to wrap up on "Dissecting the Carbon-SLO Tension in Geo-Distributed LLM Serving", the authors have provided a high-fidelity simulator and a set of SLO-aware schedulers that balance carbon and latency objectives.
Lu: They proved that using an MILP formulation for scheduling requests to datacenters at coarse time intervals, assuming load-independent latency, results in the best carbon-SLO balance with an average SLO violation of three percent <ref:2610.14571#pg2>.
Jane: It means that if you want real reductions in carbon emissions without breaking service agreements, you need to use a scheduler that understands the interplay between queueing delays and grid carbon intensity <ref:2610.14571#pg2>.
Meng: The implication for deployment is clear: don't just pick the lowest carbon intensity region; you have to model the continuous batching behavior and its impact on latency before you can deploy a schedule <ref:2610.14571#pg3>.
Lalam: They showed that while they found a way to significantly reduce emissions, they also characterized the trade-offs, showing how carbon aggressiveness directly impacts SLO violation rates across different models and system loads <ref:2610.14571#pg2>.
Tom: The paper is really about providing the tools—the simulator and the schedulers—that let you actually test this tension between carbon awareness and latency constraints in a geo-distributed setup <ref:2610.14571#pg2>.
Lu: The work provides a concrete mathematical framework for designing these systems, which is what makes it valuable for researchers looking to push the limits of how we manage large-scale AI infrastructure <ref:2610.14571#pg2>.
Jane: So if you are building or running distributed LLM services, this paper gives you a blueprint on how to approach carbon-aware scheduling in a way that respects the latency requirements of the workload <ref:2610.14571#pg3>.
Conclusion: Tom: So we’re wrapping up this paper about "Dissecting the Carbon-SLO Tension in Geo-Distributed LLM Serving." Basically, they built a way to make decisions for AI serving that balances how much electricity you use with how fast your response times are allowed to be.
Jane: That sounds really practical. So what’s actually happening here? They’re looking at giant language models and figuring out how to serve them across different data centers, like in different parts of the world, while keeping an eye on both energy and speed requirements.
Lu: The core idea is using a simulator that mimics real-world stuff—like continuous batching and network delays between regions—so they can test different scheduling policies against actual latency targets and carbon intensity measurements.
Meng: I’m interested in how they model the queuing delays. Because when you have a continuous batching setup, requests pile up, and if you don't manage that queue well, your latency spikes way beyond what it should be.
Lalam: Exactly. The simulator tracks the exact state of each datacenter engine—how many requests are waiting and how full the current batch is—which is a key piece of information they use to predict things like time-to-first-token and time-per-output-token right at the scheduling moment.
Jane: So, for someone just listening, what does this mean for deploying an AI service? Is it just about picking the dirtiest power grid region?
Tom: No, that’s too simple. The paper shows that you have to look at how much work is actually in those queues and how long the network trips between regions are before you can make a good call.
Lu: They found that using a mathematical optimization method, an MILP, they can find a scheduling strategy that hits the sweet spot between being carbon-efficient and staying within your service level objectives.
Jane: What’s the actual result of this optimization? How much carbon reduction are we talking about, and how much service quality do we give up to get it?
Lalam: They found that with this MILP approach, they can reduce emissions by up to sixty percent compared to a simple round-robin scheduling policy.
Tom: But they also found that the best trade-off means you might violate your latency targets by about three percent on average. That’s a concrete number for the cost of efficiency.
Jane: So it’s not all wins and no losses, just finding the best compromise between two competing goals, which is exactly what we see in real infrastructure problems.
Lu: They also looked at how sensitive this whole system is to things like how often you update your load information or the physical network layout you choose.
Jane: It makes me wonder what happens when you try to push the carbon reduction even further? Does it just start breaking your service agreement faster?
More episodes
- 2610.13750-Studying the Effects of Task Diversity Using Small Mathematical Worlds
- 2610.13787-Optimal Algorithms for Nonsmooth Nonconvex Stochastic Optimization with Constraints
- 2610.13799-Adaptive Variance Reduction without Knowing Oracle Smoothness
- 2610.13834-On the Design Space of Continuous Diffusion Language Models
- 2610.13956-MDN-VJEPA: Multimodal Probabilistic Joint-Embedding World Models
- 2610.14008-Generalized PINN-Based Inverse Estimation of Spatially Varying Heat Transfer Coefficients with Transfer Learning
- 2610.14016-DShuttleNet: A Badminton Doubles Dataset for Evaluating Team Coordination
- 2610.14024-Beyond a Better Score: Long-Horizon Agentic ML Development and Evaluation Protocol for Physics Time Series
- 2610.14098-From Prototype to Massing: Learning Graph Correspondence for Scalable Facade Modeling
- 2610.14120-Early Detection of Pension-Sponsor Distress from Public Filings: A Sponsor Vulnerability Index, Stress-Augmented VaR, and Dynamic Self-Investment Caps