← Latest papers
🤖 machine learning

PlexRL: Cluster-Level Orchestration of Serviceized LLM Execution for RLVR

PlexRL is a cluster-level runtime that improves the efficiency of Reinforcement Learning with Verifiable Rewards (RLVR) training by multiplexing unified LLM services across jobs to fill structural idle gaps, thereby reducing user GPU costs by up to 37.58% without expensive model migrations.

Original authors: Yiqi Zhang, Fangzheng Jiao, Tian Tang, Boyu Tian, Hangyu Wang, Qiaoling Chen, Guoteng Wang, Zhen Jiang, Peng Sun, Ping Zhang, Xiaohe Hu, Ziming Liu, Menghao Zhang, Yanmin Jia, Yang You, Siyuan Feng

Published 2026-05-21
📖 4 min read☕ Coffee break read

Original authors: Yiqi Zhang, Fangzheng Jiao, Tian Tang, Boyu Tian, Hangyu Wang, Qiaoling Chen, Guoteng Wang, Zhen Jiang, Peng Sun, Ping Zhang, Xiaohe Hu, Ziming Liu, Menghao Zhang, Yanmin Jia, Yang You, Siyuan Feng

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 are running a massive, high-tech bakery. In this bakery, you have two main types of work: baking (which requires a huge, expensive oven) and decorating (which requires a smaller, faster station).

In the world of Artificial Intelligence, specifically training "reasoning" models (like the ones that solve math problems), the "baking" is the training phase, and the "decorating" is the rollout phase (where the AI generates answers).

The Problem: The "Empty Oven" Syndrome

Currently, most AI training setups work like a bakery where every single order gets its own dedicated oven and decorating station, even if they aren't using them all the time.

  1. The "Split" Bakery: You have one team baking and another team decorating, but they work in shifts. When the bakers are working, the decorators sit idle. When the decorators are working, the bakers sit idle. You are paying for two full teams, but only one is working at a time.
  2. The "Colocated" Bakery: You put the bakers and decorators in the same room to save space. But the oven is so huge (because the AI models are massive) that the decorating team has to wait for the bakers to finish before they can even touch the counter. The oven is often oversized for the small decorating tasks, wasting energy.
  3. The "Asynchronous" Bakery: You try to have the decorators work on yesterday's cakes while the bakers work on today's. It helps a little, but eventually, the timing gets messy, and you end up with stale cakes or waiting around anyway.

The paper calls this "job-local inefficiency." Every single AI training job has these "idle gaps" where expensive computer chips (GPUs) are just sitting there doing nothing.

The Solution: PlexRL (The "Shared Kitchen" System)

The authors built a system called PlexRL. Instead of giving every AI job its own private kitchen, PlexRL turns the whole data center into one giant, shared kitchen.

Here is how it works, using our bakery analogy:

  • The Central Manager (The Scheduler): Imagine a head chef who doesn't care which bakery order is being made. They only care about the tasks. They see that Job A is currently "decorating" (using a small part of the oven) and Job B is "baking" (using the big part).
  • Time-Slicing: The manager realizes that while Job A is waiting for a tool to arrive, Job B can use that same oven for a few seconds. PlexRL quickly swaps the "state" (the recipe and the current cake) in and out of the oven.
  • No Moving the Oven: Usually, moving a giant oven to a new kitchen takes forever. PlexRL is smart: it keeps the oven in one place and just swaps the ingredients (the AI model's memory) in and out of the oven very quickly. It uses a "state manager" to keep track of where every ingredient is, whether it's on the counter (fast memory) or in the freezer (slower storage).

The Magic Trick: "Anti-Correlated" Gaps

The secret sauce is that the "idle times" of different AI jobs rarely happen at the same time.

  • Job A might be waiting for a tool call (a long pause).
  • Job B might be in the middle of intense math calculations (no pause).

PlexRL fills Job A's pause with Job B's work. It's like a taxi driver who picks up a passenger going North, then immediately picks up a passenger going South, rather than driving back to the garage empty.

The Results

The paper tested this on a massive cluster of 2,048 computer chips (GPUs) training AI models of different sizes (from small to huge).

  • Cost Savings: By filling in all those empty gaps, they reduced the cost of training by up to 37.58%. That's like getting a 37% discount on your electricity bill just by being smarter about when you turn the lights on.
  • Speed: They didn't slow down the AI's learning. The models learned just as well as before; they just got there using fewer resources.
  • Flexibility: Researchers can still try new, weird, or complex ways of training AI without having to rewrite the whole system. PlexRL handles the messy "plumbing" of moving data around so the researchers can focus on the math.

In a Nutshell

PlexRL is a system that stops treating AI training jobs like isolated islands. Instead, it treats them like a busy, shared city bus system. It ensures that the expensive "buses" (computer chips) are never running empty. By intelligently swapping different jobs in and out of the same hardware, it saves a massive amount of money and computing power without making the AI any dumber.

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 →