← Latest papers
🤖 machine learning

ML Inference Scheduling with Predictable Latency

This paper identifies critical limitations in existing ML inference scheduling approaches, specifically their coarse-grained interference prediction and reliance on static models, which lead to inaccurate latency forecasts and compromised SLOs under dynamic workloads.

Original authors: Haidong Zhao, Nikolaos Georgantas

Published 2026-06-16
📖 4 min read☕ Coffee break read

Original authors: Haidong Zhao, Nikolaos Georgantas

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Picture: The Busy Restaurant Kitchen

Imagine a high-end restaurant kitchen (the GPU) that is incredibly fast but very expensive to run. To save money, the owner wants to cook as many meals as possible at once (improving utilization).

In this kitchen, orders come in for different dishes (like Machine Learning models). To be efficient, the chef groups similar orders together into a single "batch" to cook them all at once. For example, instead of cooking one burger, then two fries, then one burger, they cook a tray of five burgers at the same time.

However, the kitchen has a problem: Interference.
If the chef tries to cook a huge tray of burgers and a tray of delicate soufflés at the exact same time on the same stove, they might get in each other's way. The heat might get uneven, or the chef might have to switch tools too often. This slows everything down, causing the food to arrive late.

In the world of AI, "late food" means latency. If a self-driving car or a video call gets a delayed answer because the kitchen was too crowded, that's a failure. The goal of this paper is to figure out how to schedule these cooking batches so the kitchen stays busy without making the food late.

The Problem: Guessing is Dangerous

The paper argues that current methods for predicting how much "crowding" (interference) will happen are flawed in two main ways:

1. The "Static Snapshot" Problem (Coarse-Grained)

The Analogy: Imagine you are a traffic controller. You look at a map and see a red truck and a blue car currently on the highway. You predict they will drive side-by-side for the whole trip.
The Reality: In the kitchen, the red truck (Batch 1) might leave the highway after 10 seconds, and a giant semi-truck (Batch 3) might jump in and stay for 5 minutes.
The Paper's Claim: Current AI schedulers are like that traffic controller. They look at who is in the kitchen right now and assume they will stay that way. They ignore the fact that batches come and go at different times.

  • Result: The prediction is wrong. The system thinks the kitchen will be calm, but suddenly a new, heavy batch arrives, causing a traffic jam and late deliveries.

2. The "Old Map" Problem (Non-Adaptive/Static Models)

The Analogy: Imagine you trained a robot chef to predict cooking times using a menu from last year. Last year, everyone ordered burgers. This year, everyone is ordering complex seafood.
The Reality: The robot chef still thinks, "Oh, it's just burgers," and predicts the cooking time will be fast. But because the menu changed, the robot is wrong.
The Paper's Claim: Current AI models are "static." They are trained once on old data and then never updated. If the types of requests change (e.g., new AI models are added, or the number of orders changes), the old model becomes inaccurate.

  • Result: The system keeps making bad guesses because it's using an outdated map for a changing world.

What the Authors Did (The Experiment)

The authors set up a test kitchen (using an NVIDIA GPU) to see how bad these two problems really are.

  1. Testing the "Snapshot" issue: They ran simulations where batches arrived and left at different times. They found that if you ignore these changes, your prediction of how long a task will take can be off by a huge margin (sometimes more than 60% error). It's like guessing a 10-minute drive will take 16 minutes because you didn't know a traffic light was about to turn red.
  2. Testing the "Old Map" issue: They trained a model on one set of dishes, then tried to predict times for a completely different set of dishes. The old model failed miserably. However, when they let the model "learn on the fly" (Online Learning)—updating its predictions as it saw new data—it got much better at handling the changes.

The Conclusion

The paper concludes that to run an efficient AI kitchen without late deliveries, we need to stop using "dumb" schedulers that:

  1. Ignore the fact that the crowd in the kitchen changes every second.
  2. Refuse to learn from new types of orders.

Instead, we need a smart scheduler that:

  • Watches the kitchen dynamically (tracking who arrives and leaves).
  • Learns and updates its predictions in real-time as the workload changes.

By doing this, we can keep the GPU (the kitchen) busy and efficient while still guaranteeing that every order (every AI request) gets its answer on time.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →