Async GRPO Setup Left Some Training Runs Without the Full Data Mixture

yb2698 · x · 2026-11-09

The author details how their training setup (fixed number of steps plus async GRPO) meant not every run saw the entire training mixture, and lists the task ranges each model actually encountered:

Each step trains on as many finished rollouts as fit its token budget. Longer rollouts (TwIL's long reasoning, the hermes harness) mean fewer tasks per step, and tasks ran in a fixed order, so some runs never reached traj2envs.

Original post →

More from Research

Research channel →