← Latest papers
💻 computer science

Observation, Not Prediction: Conversation-Level Disaggregated Scheduling for Agentic Serving

The paper introduces ConServe, a scheduling framework that shifts the scheduling unit from individual turns to entire conversations to eliminate the need for predicting unknown future costs, thereby reducing latency and improving energy efficiency by leveraging a stable two-phase structure of compute-bound prefill and memory-bound decoding.

Original authors: Jianru Ding, Ryien Hosseini, Pouya Mahdi Gholami, Mingyuan Xiang, Henry Hoffmann

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

Original authors: Jianru Ding, Ryien Hosseini, Pouya Mahdi Gholami, Mingyuan Xiang, Henry Hoffmann

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

Imagine you run a busy restaurant kitchen. In the old days, every order was simple: a customer walks in, you cook the meal, and they leave. You could easily manage the kitchen because every order took roughly the same amount of time and effort.

But now, imagine your customers are "AI Agents." They don't just order a meal; they start a complex project.

  1. The First Turn (The Big Brief): The customer sits down and gives you a massive, 50-page instruction manual. This takes a long time to read and understand (the "Prefill").
  2. The Middle Turns (The Tool Calls): The chef starts cooking, then stops to call a supplier, wait for a reply, check a recipe, and call back. These steps are short, but they happen over and over again.
  3. The Final Turn (The Result): Finally, the dish is ready to serve.

The Problem: The Old Way of Scheduling

Current kitchen managers (AI systems) treat every single step as a separate order. Every time the chef stops to call a supplier, the manager has to decide: "Do I let the chef finish this step right here in the main kitchen, or do I send this specific step to a different, specialized station?"

The problem is that the manager has to guess how long that step will take or how much memory it will need before it happens. If they guess wrong, they send the step to the wrong station, causing a traffic jam. It's like a traffic cop trying to direct cars by predicting exactly how fast each driver will drive before they even start moving.

The Solution: ConServe (The Conversation-Level Approach)

The paper introduces a new system called ConServe. Instead of managing every single step separately, ConServe manages the entire conversation as one single unit.

Here is how ConServe changes the rules using a simple two-phase plan:

Phase 1: The Heavy Lifting (The Prefill)
When the customer first arrives with that 50-page manual, ConServe sends them immediately to a super-fast, high-power station (a powerful GPU). This station is built specifically for reading huge documents quickly. It reads the manual, understands the context, and creates a "memory map" (called a KV cache) of everything needed.

Phase 2: The Long Tail (The Rest of the Conversation)
Once that initial map is made, ConServe says: "Okay, the heavy lifting is done. Now, this entire conversation belongs to one specific, smaller, energy-efficient station."

  • The "memory map" is moved exactly once to this new station.
  • From that moment on, every single follow-up step (the tool calls, the short updates) happens right there on that same station.
  • The system never guesses again. It doesn't matter if the next step is short or long; the conversation stays pinned to that one station until the job is done.

Why This is Better (The Analogy)

Think of it like a delivery truck:

  • The Old Way: You try to predict if the next package is heavy or light. If you guess wrong, you send a small truck for a heavy load, or a big truck for a tiny package. You waste gas and time.
  • ConServe: You load the truck once at the start. You drive the truck to the destination and park it there. All the subsequent packages for that specific customer are loaded onto that same truck. You don't need to predict the weight of the next package; you just keep the truck running efficiently.

The Results

The paper tested this on real AI agent workloads and found:

  1. Speed: It reduced the time it takes for the customer to see the first real result (not just a tool call) by 51%. It's like getting your food 50% faster because the kitchen isn't confused about where to put the ingredients.
  2. Efficiency: It saved 7.5% energy. By using a powerful station only for the big initial reading and a cheaper station for the rest, it wastes less electricity.
  3. Reliability: Because the system doesn't have to guess (predict) what will happen next, it never makes "wrong turn" errors. The old systems would crash or slow down if their predictions were off; ConServe just keeps going because it relies on what it can actually see right now.

In short: ConServe stops trying to predict the future of every tiny step in an AI conversation. Instead, it treats the whole conversation as one job, handles the heavy start with a powerful engine, and then lets a steady, efficient engine finish the rest.

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 →