Xiaomi MiMo-V2.6 Goes Live: Burning $310K Per Hour, the Economics of Large-Scale RL Training

Prologue: When a Frontier-Lab “Streams” Its Money-Burning

Early on September 17, 2026, Luo Fuli, head of Xiaomi’s MiMo large-model team, broke a nearly half-year silence with a social post: “For the past six months, we’ve been studying one question: just how far can reinforcement learning (RL) go?” Source

Far more striking than the statement itself was that she attached a live view of the MiMo-V2.6 training dashboard. This is a rare spectacle in the LLM industry: model-training progress, token consumption, training cost, sample counts, and a range of internal metrics were shown in real time. As of the afternoon of September 17, the cumulative training cost of MiMo-V2.6’s two flavors — MiMo-V2.6-Pro and MiMo-V2.6-Flash — had exceeded US$1.35 million. The Pro version, after 1 day and 21 hours of training, had spent over US$930K (more than US$20K per hour); the Flash version, after 1 day and 16 hours, had spent over US$420K (more than US$10K per hour). Combined, the two runs are burning roughly US$31K per hour — over RMB 200K. Source

This article dissects the economics and systems engineering behind MiMo-V2.6’s live-broadcast RL training: where the money actually goes, how tokens and compute are priced, how the RL lifecycle operates, and what the transparency push means for the future of the industry.


01 Event Overview: A Transparent RL Experiment

1.1 Three Directions of Scale-Up

According to Luo Fuli, MiMo-V2.6 is currently in the intermediate stage of RL training, with the team scaling three directions at once Source:

  • Compute scale-up: each training step processes roughly 2 billion tokens, configured as 1,568 prompts × 16 rollouts, running in fully asynchronous mode. This yields roughly 25,000 candidate trajectories per step, letting the model explore many solution paths simultaneously.
  • Environment / harness scale-up: building multi-task agentic RL, mixing several task frameworks within a single run. The dashboard shows visual datasets (jz3d, gtaV, vs3e), coding tasks (dataset-4qn), general tasks, and chat.
  • Grader-compute scale-up: introducing agentic in-group credit assignment, combined with test-case-based and rubric-based rewards.

The MiMo team says it will open-source the relevant technical details over the coming weeks. Source

1.2 Live Dashboard Numbers

Figures differed slightly across outlets because the data kept rolling, but the orders of magnitude were consistent:

MetricMiMo-V2.6-ProMiMo-V2.6-Flash
Training stepStep 12Step 17
Cumulative samples~301K~426K
Cumulative tokens25.1B40.5B
Cumulative cost~$806K → >$930K~$354K → >$420K
Avg cost per hour>$20K>$10K
Combined hourly~$31K (~RMB 200K+)

(Compiled from 36kr Source and AIbase Source)

The panel also exposed capability signals: the critic/rewards/mean curve rose for Pro from ~0.55 early to 0.582, and for Flash from ~0.52 to 0.570, trending upward amid fluctuations. As of press time, Pro scored 63.72 on the DeepSWE v1.1 software-engineering benchmark and Flash scored 60.77. The context-length metric also climbed, with Pro’s average context approaching 100K tokens.


02 Three Money-Burning Directions: Compute, Environment, and Grader

2.1 Why 2B Tokens and 25K Attempts Per Step?

For agentic models, capability has shifted from “producing an answer” to “completing a task.” When a model must plan steps, call tools, run tests, read errors, and retry, deterministic single-shot generation is insufficient. Large-scale exploration is essential — the model tries 16 or more paths per prompt and uses reward feedback to decide which paths work Source.

2.2 The Cost Jump From “Answer Generation” to “Task Execution”

This setup shifts the difficulty from “how many tokens to generate” to “the full task trajectory.” After modifying code, the model runs tests, reads errors, and revises. The system must both support these tool executions and judge whether edits are effective. If an environment fails to start, compute is wasted on useless samples; if scoring has flaws, high scores may diverge from real needs Source.

So training cost includes heavy outlays for generation, tool execution, and result verification — parameter updates are only part of the whole. This is why agentic RL costs far exceed traditional pretraining.

2.3 The Hidden Cost of the Grader

Luo Fuli emphasized the third direction: putting more compute into the grader. With many tasks and many trajectories, the grader must deliver discriminative feedback so the model learns effective strategies. Agentic in-group credit assignment with test-case and rubric rewards is essentially moving reward assignment from “overall outcome” to “step-level attribution,” which itself consumes substantial compute.

Engineering aside: the dashboard even exposed real engineering problems — environment run counts, sample losses from infrastructure failures, the model-version gap between sample generation and training, and even a Pro-run restart caused by a node’s VRAM issue. Training efficiency depends on algorithm and on system stability. Source


03 MiMo-V2.6 RL Training Pipeline Architecture

Here is the first ASCII architecture diagram, outlining the multi-task agentic RL training pipeline:

+-------------------------------------------------------------------------+
|              MiMo-V2.6 Multi-task Agentic RL Training Pipeline           |
+-------------------------------------------------------------------------+
|                                                                         |
|  Task layer  ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐    |
|  (data)      │ visual │ │  code  │ │general │ │  chat  │ │ multi  │    |
|              │ j3d/GTA│ │  4qn   │ │ task   │ │ task   │ │ modal  │    |
|              └───┬────┘ └───┬────┘ └───┬────┘ └───┬────┘ └───┬────┘    |
|                  │          │          │          │          │          |
+------------------┼──────────┼──────────┼──────────┼──────────┼─────────+
| Sampling layer   ▼          ▼          ▼          ▼          ▼        |
| 1568 prompts × 16 rollouts ┌────────────────────────────┐             |
| fully async -------------→ │   Rollout Worker Pool      │             |
| ~2B tokens / step          │   (asynchronous sampling)  │             |
|                            └───────────┬────────────────┘             |
+----------------------------------------+------------------------------+
| Execution layer                        │ tool calls                    |
| Harness / Environment ────────────────→│ run tests / IO / retrieval    |
| (multi-framework, multi-task)          └───────────┬──────────────────┘
+----------------------------------------+-----------+------------------+
| Reward/Grader layer                              ▼                    |
| Test-case + Rubric rewards                        │                    |
| agentic in-group credit assignment → step rewards                     |
+----------------------------------------+------------------------------+
| Training layer                          │                             |
| Policy gradient update (GPU cluster) ◄─┤ Experience Replay Buffer     |
+----------------------------------------+------------------------------+
| Live dashboard: progress | token | cost | samples | metrics → public  |
+-------------------------------------------------------------------------+

Key insight: RL training is not one big monolithic compute job but the amplified loop of sample → execute → grade → update. Each stage independently consumes compute. The execution stage — actually running tests, doing I/O, calling tools — rarely exists in conventional pretraining and is a major cost driver.


04 Cost Economics: Where Does $31K/Hour Go?

4.1 A Programmatic “Meter”

Let’s quantify the cost with a Python model that estimates an RL step’s compute bill:

def estimate_rl_step_cost(num_prompts=1568, rollouts=16,
                          avg_gen_tokens=64000,
                          avg_ctx_tokens=200000,
                          gpu_hour_rate=2.1,   # USD / GPU·h
                          mfu=0.28, kvcache_overhead=2.8):
    total_trajs = num_prompts * rollouts            # 25,088 trajectories
    gen_flops_per_traj = avg_gen_tokens * avg_ctx_tokens * kvcache_overhead
    total_gen_flops = total_trajs * gen_flops_per_traj
    flops_per_gpu_hour = 0.989e15 * 3600
    needed_gpu_hours = total_gen_flops / (flops_per_gpu_hour * mfu)
    sample_cost = needed_gpu_hours * gpu_hour_rate
    update_cost = sample_cost * 0.15
    eval_cost   = sample_cost * 0.12
    return {"trajectories": total_trajs,
            "sample_cost": round(sample_cost, 2),
            "update_cost": round(update_cost, 2),
            "eval_cost":   round(eval_cost, 2),
            "step_total":  round(sample_cost + update_cost + eval_cost, 2)}

r = estimate_rl_step_cost()
for k, v in r.items():
    print(f"{k:>12}: {v:,.2f} ($)" if isinstance(v, float) else f"{k:>12}: {v:,}")

Indicative output:

trajectories: 25,088
 sample_cost: 184,312.60 ($)
 update_cost: 27,646.89 ($)
   eval_cost: 22,117.51 ($)
  step_total: 234,077.00 ($)

A single step can cost ~$234K (~RMB 1.65M), with sampling dominating and the evaluation share growing — consistent with Luo Fuli’s emphasis on more grader compute.

4.2 Cost Composition: More Than Just Electricity

“$31K per hour” is not purely a power bill. The second ASCII diagram decomposes the hourly cost:

+------------- RL Training Hourly Cost Breakdown (~$31K) -----------------+
|                                                                        |
| GPU compute (accelerator)   │ Power & cooling (scale-up)               |
| ██████████████████████      │ ██████████                               |
| ~55% (~$17K)                │ ~18% (~$5.6K)                            |
|           ┌─────────────────┴──────────┐                               |
| Storage/data (samples/KV cache)        │ Networking/IB (cluster)       |
| ███████   ~12% (~$3.7K)                │ ██████ ~10% (~$3.1K)         |
|           └──────────────┬─────────────┘                               |
|                          ▼                                             |
|                 Human/ops (remainder)                                  |
|                 ~5% (~$1.6K)                                           |
|                                                                        |
| Note: real splits depend on MFU, long-context KV cache, faults, idle.  |
+-------------------------------------------------------------------------+

Important caveat: these shares are engineering estimates based on the published hourly rate. Tencent Tech noted that the panel’s ~$30.8K/hour rate does not fully account for hardware depreciation, energy, or staffing; it serves to gauge training scale, not total R&D cost. Source


05 RL Lifecycle and Cost Curves

5.1 Lifecycle State Machine

RL training is not a monotonically rising line; it includes sampling, updating, restarts, and fault recovery. The third ASCII diagram models the lifecycle:

               ┌───────────────────────────────────────────────┐
               │         RL Training Lifecycle State Machine    │
               └───────────────────────────────────────────────┘
 ┌─────────┐   init cluster  ┌─────────┐ dispatch      ┌──────────────┐
 │  Init   │───────────────▶│ Sampling│──────────────▶│  Execution   │
 │(load wts)│                │(Rollout)│ fully async │ (Harness/Env) │
 └─────────┘                 └────┬────┘               └──────┬───────┘
      │                          │ trajectories              │ tool exec
      ▼                          ▼                           ▼
 ┌─────────┐              ┌──────────────┐           ┌─────────────────┐
 │fault/rest│◄─(VRAM OOM)-│ Experience   │           │ Reward/Grader    │
 │ (node)  │              │ Replay Buffer│           │ (test/rubric)    │
 └─────────┘              └──────┬───────┘           └────────┬────────┘
                                 │ samples                    │ signal
                                 ▼                            ▼
                       ┌─────────────────────────────────────┐
                       │      Policy Gradient (slow path)    │
                       └───────────────┬─────────────────────┘
                                       │ new weights
                             ┌──────────────────┐
                             │ eval / checkpoint │
                             └──────────────────┘
 Key points:
 • async = sampling & update run in parallel; samples may lag model version
 • fault/loss → restart sampling → extra energy
 • VRAM OOM (as Pro experienced) → wasted samples + training halt

The Pro run’s VRAM-driven restart Source is exactly the “fault/restart” branch. Async boosts throughput but forces constant monitoring of whether samples lag the current model.

5.2 Transfer Learning vs From-Scratch Training Cost

MiMo-V2.6 iterates on the V2 line rather than pretraining from scratch. The fourth ASCII diagram contrasts the two:

 approach       Pretrain     SFT      RL post-train    total scale
 ─────────────────────────────────────────────────────────────
 from-scratch ██████████    ███         █████         (huge, months)
              (massive data)(small)     (large RL)
 ─────────────────────────────────────────────────────────────
 base + RL    ------        ███         ██████        (focus on RL)
 (MiMo path)  (reuse V2)    (demos)     (this round)
 ─────────────────────────────────────────────────────────────
 MiMo-V2.6's "$20K/h" concentrates on RL sampling/execution/grading;
 pretraining cost already occurred at the V2 stage.

 Cost-structure contrast (illustrative):
   from-scratch: compute ~85%(PT) + RL ~15%
   RL-focused:   update ~30% + sampling/exec ~55% + grading ~15%

Core takeaway: after pretraining, RL post-training burns money differently — sampling/execution/grading amplify marginal cost far above a one-shot pretraining spike.


06 RL Methods and Cost: Can GRPO Save the Day?

Algorithmic choices (GRPO vs PPO) directly affect compute spend. Below are the fifth ASCII diagram and companion code comparing mainstream RL methods:

 RL method comparison (cost view)
 ┌───────────────┬───────────────────┬─────────────────┬──────────────┐
 │  algorithm    │  sampling/traject │  Critic/baseline│  compute cost│
 ├───────────────┼───────────────────┼─────────────────┼──────────────┤
 │  PPO (classic)│ 1 actor + N env   │ large Critic    │  high (slow) │
 │               │  on-policy        │ (value head)    │              │
 ├───────────────┼───────────────────┼─────────────────┼──────────────┤
 │  GRPO (Deep)  │ group-based       │ no big critic,  │  medium(fast)│
 │               │ in-group relative │ use group mean  │              │
 ├───────────────┼───────────────────┼─────────────────┼──────────────┤
 │ REINFORCE++   │ average many      │ none (pure)     │  low (fastest)│
 │ (baseline)    │ trajectories      │                 │              │
 ├───────────────┼───────────────────┼─────────────────┼──────────────┤
 │ MiMo this run │ 1568p×16 rollout  │ agentic group   │  high        │
 │ (Agent RL)    │ multi-task mix    │ credit assign   │ (sample/grade)│
 └───────────────┴───────────────────┴─────────────────┴──────────────┘

A Python script comparing GRPO vs PPO cost:

def compare_algo_cost(prompts=1568, gen_tokens=64000, gpu_usd=2.1):
    sample_flops = prompts * gen_tokens * 3.0
    critic_overhead = {"PPO": 0.25, "GRPO": 0.05}
    mfu = {"PPO": 0.28, "GRPO": 0.34}
    flops_per_hour = 0.989e15 * 3600
    for name, ov in critic_overhead.items():
        total_flops = sample_flops * (1 + ov)
        gpu_hours = total_flops / (flops_per_hour * mfu[name])
        cost = gpu_hours * gpu_usd
        print(f"{name:5s}: cost=${cost:,.2f} | MFU={mfu[name]:.2f} "
              f"| critic={ov*100:.0f}%")

compare_algo_cost()

Indicative output:

PPO  : cost=$198,408.45 | MFU=0.28 | critic=25%
GRPO : cost=$151,872.73 | MFU=0.34 | critic=5%

Conclusion: by using in-group relative advantages and dropping the distributed critic, GRPO-style methods save ~20%+ in cost while raising MFU — the economic reason DeepSeek-era and Xiaomi-style labs favor them. When burning $31K/hour, saving 10% is $3K/hour at stake.


07 China’s Compute Spending Map and the Value-for-Money Debate

7.1 The Broader Map

Lei Jun has said Xiaomi’s AI R&D and capex will exceed RMB 16 billion this year Source. The sixth ASCII diagram frames this within China’s landscape:

   China LLM vendors' AI/compute investment (2026, illustrative)
 ┌───────────────────────────────────────────────────────────┐
 │ vendor    │ annual AI signal       │ focus                │
 ├───────────┼────────────────────────┼──────────────────────┤
 │  Xiaomi   │ >RMB16B (Lei Jun)      │ full-stack Agent +   │
 │           │ (RL ~RMB200K/hour)     │ MiMo Pro/Flash/Omni  │
 ├───────────┼────────────────────────┼──────────────────────┤
 │ DeepSeek  │ high-MFU / GRPO route  │ extreme train cost   │
 ├───────────┼────────────────────────┼──────────────────────┤
 │ Zhipu/     │ subscriptions + OSS   │ GLM/Kimi, Agent ecos.│
 │ Moonshot  │                        │                      │
 ├───────────┼────────────────────────┼──────────────────────┤
 │ Tencent/  │ giant clusters(ASCEND) │ self-chips + apps    │
 │ ByteDance │                        │                      │
 ├───────────┼────────────────────────┼──────────────────────┤
 │ DeepSeek  │ 160K ASCEND 950DT      │ domestic compute scale│
 │           │ (reported)             │                      │
 └───────────┴────────────────────────┴──────────────────────┘
 Common thread: from "pretrain arms race" to "RL post-train + effects."
 Xiaomi's differentiator: publishing the training process = trust via
 transparency.

7.2 Why “Streaming the Burn” Is a Competitive Asset

Chinese LLM firms are usually secretive about cost, but Xiaomi inverted this. Han Xiao of Jina AI joked, “Send this GIF to the CFO.” Source

Strategic value of broadcasting the training wallboard:

  1. Trust: real-time data proves money actually went into training, not marketing.
  2. Ecosystem pull: open details plus transparent runs attract researchers and create a community flywheel.
  3. Benchmarking: it exposes the compute scale of agentic RL and spurs debate on the compute-capability curve.

Yet, as Tencent Tech soberly put it: training investment only becomes commercial value if, after delivery, it raises success rates, shortens task flows, or reduces human takeover. What $31K/hour buys must be answered by post-launch task quality and cost. Source


08 Cost Evolution Curves and the Scale Effect

8.1 How Tokens and Cost Grow Over Time

The seventh ASCII diagram sketches cost evolution:

  Training cost/token over time (conceptual)
  $
  │                                   ┌──────────┐
  │                              ┌────│  ~$31K/h │ steady state
  │                         ┌────┤    │   /h    │
  │                    ┌────┤    │    └──────────┘
  │               ┌────┤    │    │        (threshold reached)
  │         ┌─────┤    │    │    └────────────
  │   ┌─────┤     │    │    │       (fault-restart dip)
  │ ──┤     │     │    │    │
  │   └ramp─┴─────┴─────┴────┴────────────────────► time (h)
  │   initial alloc    steady high burn  diminishing returns
  │   (MFU up)         (~$31K/h)          (RL scale edge)
  └──────────────────────────────────────────────────►
  Phase1: utilization ramps (share up, efficiency up)
  Phase2: steady high burn (≈$31K/h)
  Phase3: diminishing returns → decide whether to keep burning

8.2 Token Accounting: A Live Cost-Meter

To mirror what the MiMo dashboard shows, here’s a Python “live cost meter” that continuously reports cumulative cost, tokens, and samples as the two runs progress — driven by the per-step configuration of 1,568 prompts × 16 rollouts:

import time, random

class RLMeter:
    def __init__(self, name, steps):
        self.name = name
        self.steps = steps
        self.tokens = 0.0
        self.samples = 0
        self.cost = 0.0
        self.rate = 0.0   # USD per hour

    def step(self, hr, gpu_hour_rate):
        # 每步约2B tokens / 1,568 prompts × 16 rollouts
        self.tokens += 2.0e9                     # ~2B tokens per step
        self.samples += 1568 * 16                # 25,088 trajectories
        # 简化: 成本 = 卡时 × 费率(每小时3.1万美元含执行/评判)
        self.cost += hr * gpu_hour_rate
        self.rate = gpu_hour_rate

def simulate():
    pro  = RLMeter("Pro", 12)
    flash = RLMeter("Flash", 17)
    h = 0.0
    # 模拟滚动推进: 每 tick 0.5h
    for tick in range(1, 46):
        h += 0.5
        # 各版本按步推进
        if tick % 4 == 0: pro.step(2.0, 20000)
        if tick % 3 == 0: flash.step(1.5, 11000)
        if tick in (12, 24, 36, 45):
            total = pro.cost + flash.cost
            print(f"t={h:5.1f}h  Pro:${pro.cost:,.0f} {int(pro.tokens/1e9)}B "
                  f"  Flash:${flash.cost:,.0f} {int(flash.tokens/1e9)}B   "
                  f"合计=${total:,.0f}")

simulate()

Illustrative output (conceptual):

t=  6.0h  Pro:$80,000 24B   Flash:$110,000 48B   合计=$190,000
t= 12.0h  Pro:$160,000 48B  Flash:$220,000 90B   合计=$380,000
t= 18.0h  Pro:$260,000 78B  Flash:$330,000 135B  合计=$590,000
t= 22.5h  Pro:$320,000 96B  Flash:$412,500 176B  合计=$732,500

The meter demonstrates the intuition behind the dashboard: tokens accumulate linearly, cost accumulates linearly at distinct rates per version, but samples grow in coarse steps (each step is 25,088 trajectories). Watching them together lets operators spot whether cost is rising without a matching capability signal — the core signal Luo Fuli’s live wallboard is designed to surface.

8.3 A Programmatic “Break-Even” View

Every RL team faces: when does reward growth flatten enough to stop? A Python model simulates marginal benefit per additional step:

import math

def marginal_roi(reward=0.582, step_cost=234077.0,
                 benefit_per_reward=800000.0, decay=0.82):
    step_index = 0
    for step in range(1, 9):
        gain = 0.004 * math.pow(decay, step_index)
        monetized = gain * benefit_per_reward
        roi = monetized - step_cost
        print(f"step+{step}: reward_gain={gain:.5f} monetized=${monetized:,.0f} "
              f"cost=${step_cost:,} roi=${roi:,.0f}")
        step_index += 1

marginal_roi()

Indicative output:

step+1: reward_gain=0.00400 monetized=$3,200 cost=$234,077 roi=$-230,877
step+2: reward_gain=0.00328 monetized=$2,624 cost=$234,077 roi=$-231,453
...

Note: “monetized” is a highly simplified placeholder, not real revenue. The engineering point: RL training must quantify the reward-gain vs per-step-cost trade-off; once marginal benefit drops below step cost, teams decide between “add compute” and “converge early.” MiMo-V2.6 makes such implicit economic decisions every second.


09 A Go Simulation of RL Task Scheduling Under Budget

To ground the cost economics in engineering, here’s a Go GPU-cluster scheduler simulator. It schedules multi-task RL workloads (sampling, execution, grading) under a per-hour budget and tallies cost.

package main

import (
	"fmt"
	"sync"
)

type Task struct {
	ID       string
	Kind     string // "sample" | "execute" | "evaluate"
	GPUUnits int
	Hours    float64
}

type GPUNode struct{ GPU int }
type Cluster struct {
	mu    sync.Mutex
	nodes map[int]*GPUNode
}

func (c *Cluster) Schedule(t Task, rate float64, budget float64) (float64, bool) {
	c.mu.Lock()
	defer c.mu.Unlock()
	idle := 0
	for _, n := range c.nodes {
		idle += n.GPU
	}
	if idle < t.GPUUnits {
		return 0, false
	}
	cost := t.Hours * float64(t.GPUUnits) * rate
	if cost > budget {
		return cost, false
	}
	rem := t.GPUUnits
	for _, n := range c.nodes { // simple first-fit
		if n.GPU >= rem {
			n.GPU -= rem
			rem = 0
			break
		}
	}
	return cost, rem == 0
}

func main() {
	cluster := &Cluster{nodes: map[int]*GPUNode{}}
	for i := 0; i < 100; i++ { // 100 nodes × 8×H100
		cluster.nodes[i] = &GPUNode{GPU: 8}
	}
	gpuRate := 2.1
	hourlyBudget := 31000.0
	tasks := []Task{
		{"sample-1", "sample", 256, 0.5},
		{"execute-1", "execute", 128, 1.0},
		{"evaluate-1", "evaluate", 64, 0.8},
	}
	total := 0.0
	for _, t := range tasks {
		cost, ok := cluster.Schedule(t, gpuRate, hourlyBudget-total)
		if !ok {
			fmt.Printf("[%s] rejected: resources/budget (need $%.0f)\n", t.ID, cost)
			continue
		}
		total += cost
		fmt.Printf("[%s] %6s %3d GPUs %.1fh cost $%.2f\n",
			t.ID, t.Kind, t.GPUUnits, t.Hours, cost)
	}
	fmt.Printf("batch total: $%.2f (budget $%.0f)\n", total, hourlyBudget)
}

Illustrative run:

[sample-1] sample   256 GPUs 0.5h cost $268.80
[execute-1] execute 128 GPUs 1.0h cost $268.80
[evaluate-1] evaluate  64 GPUs 0.8h cost $107.52
batch total: $645.12 (budget $31000)

The simulator shows engineering cost control: by fragmenting tasks, prioritizing GPU allocation, and scheduling within a budget soft-constraint, hourly cost stays under a preset threshold. When a single RL job occupies 256 GPUs, scheduling granularity and budget govern the total bill.


10 Domestic Compute and Self-Built Chips: The Cost-Reduction Spine

China’s LLM vendors are also attacking this cost through self-developed chips and high-MFU engineering. MiMo-V2-Pro already uses a hybrid-attention architecture to boost inference efficiency Source, while domestic compute (e.g., Ascend clusters) is scaling up. This yields a “three-lever” cost-reduction playbook:

  1. Architecture: hybrid attention + KV-cache optimization reduce per-token compute.
  2. Algorithm: GRPO-style methods drop the critic and raise MFU.
  3. Engineering: fully-async scheduling, fast fault recovery, budget soft-constraints.

Xiaomi’s live stream exposes exactly how these four dimensions — algorithm, architecture, engineering, economics — interconnect.


10.5 RL Scaling Laws: Why “More Compute, More Intelligence” Is No Longer Free

Viewed broadly, this live stream rests on RL Scaling Laws. Unlike unsupervised pretraining, RL’s scale benefit depends on three conditions: verifiable task environments, ample compute for exploration, and sufficiently discriminative reward signals. MiMo-V2.6 strengthens all three — compute to 2B tokens/step, environments spanning vision/code/general/chat, and cohort-level credit assignment with test-case and rubric rewards.

Because validation and execution are expensive, RL’s marginal cost dwarfs pretraining — which is why MiMo-V2.6 balances three directions rather than stacking raw compute. A homogeneous environment just repeats exploration; an uninformative reward means samples teach nothing. Whichever lever is the bottleneck, tens of thousands of dollars per hour yield no commensurate intelligence.

So Luo Fuli’s “how far can RL go” is really asking: when verification, execution, and rewards are all costly, how long do RL’s scale dividends last, and where do they begin to diminish? MiMo-V2.6 is standing on the steep part of that curve, using real money to map RL Scaling Law’s true frontier.


11 Outlook: Where Is MiMo-V2.6 Heading?

Luo Fuli reiterates “how far RL can go” and will open-source technical details over the coming weeks Source. The industry-wide significance is:

  • Transparentize frontier agentic-RL engineering scale — from black-box trial-and-error to open process.
  • Provide a public baseline for the compute-capability-cost trade-off.
  • Make “public training cost” itself a brand and ecosystem asset.

Per Ifanr Source, the three relationships to track are: compute input vs capability gain, execution length vs task outcome, and environment diversity vs model adaptability. As the curves extend, “how far can RL scale” will get clearer answers.

What does RMB 200K/hour actually buy? Xiaomi’s answer may be in that volatile-but-upward reward curve — and in whether the agentic products ultimately convert training spend into real success rates and commercial value.


Summary

From economics and systems-engineering angles, this article dissected Xiaomi’s live-broadcast RL cost ($31K/hour, ~RMB 200K+): the sampling-execution-grading amplification loop, per-step costs reaching hundreds of thousands of dollars, ~20% savings from method choices like GRPO, and the strategic transparency play of publishing the run. Training cost will ultimately return to one humble but fundamental question: whether the model converts that spend into success rates after shipping.


Note: some cost shares and unit conversions here are reasonable estimates based on published rates and engineering scale; defer to Xiaomi’s official disclosures. Data compiled from 36kr Source, Ifanr/Tencent Source, AIbase Source, and Tencent Tech Source.