CoT Distillation and Rejection-Sampling FT
The two cheaper-than-RL routes to a reasoning small model. CoT distillation SFTs a student on a strong teacher's <think> traces — no RL — which is how DeepSeek-R1-Distill-Qwen-32B beat OpenAI o1-mini. Rejection-sampling FT (RFT/RAFT) generates candidates, filters by a verifiable reward, and retrains on the winners — simpler and more stable than GRPO, and per arXiv:2504.11343, surprisingly competitive with it. The three-way decision: distillation vs RFT vs GRPO.
CoT distillation is the cheapest path to a reasoning small model that works at scale: a strong reasoning teacher (DeepSeek-R1, o1, Claude/GPT with thinking) emits
The headline result: DeepSeek-R1-Distill-Qwen-32B beats OpenAI o1-mini on several benchmarks (incl. AIME 2024 and MATH-500), achieved via SFT on ~800K curated reasoning samples distilled from R1 — NO RL on the student. A 32B model trained with nothing more than supervised fine-tuning on a stronger model's traces outperforms a frontier compressed-reasoning product. This single fact made distillation the default, accessible recipe. The R1-Distill family (Qwen 1.5B–70B, Llama 8B/70B) demonstrated the recipe scales from consumer-GPU sizes to frontier-adjacent quality.
Rejection-sampling fine-tuning (RFT / RAFT) is the middle path: iteratively fine-tune on only POSITIVELY-REWARDED candidates. Generate N candidates per problem with the current model, filter by a verifiable reward (math checks, code passes tests, answer matches), retrain (SFT) on the winners, repeat. Same data-generation machinery as GRPO (rollouts, verifiable reward) but a radically different training step: GRPO computes a policy gradient over ALL rollouts (learns from successes AND failures); RFT DISCARDS the failures and supervises on the successes only. You keep the reward; you discard the gradient noise.
The arXiv:2504.11343 finding: a simple rejection-sampling baseline is SURPRISINGLY COMPETITIVE with GRPO and PPO on math reasoning (same base/data/compute) — close enough that RFT's simplicity and stability make it a legitimate TERMINAL choice, not merely a warmup before 'graduating' to GRPO. RFT is cheaper (no policy-gradient machinery, no critic, no KL tuning) and structurally more stable (the training step is SFT, which does not diverge the way policy gradients do; RFT's worst cases — small accepted set, wrong reward — are diagnosable data problems, whereas GRPO's worst case is a silent mode collapse that ruins the model while the reward looks fine). RFT trades expressivity (ignores failures) for stability + diagnosability. Simpler methods should not be dismissed.
The three-way decision — distillation vs RFT vs GRPO — by three axes: (1) strong teacher available? Yes → distillation (cheapest, consider first). (2) reward verifiable? Yes → RFT & GRPO available; No → FT13 preference territory, not reasoning FT. (3) compute/stability: constrained/must-not-diverge → RFT; large budget/willing to tune KL/push frontier → GRPO. In one line: distillation = cheapest (have teacher, don't need to exceed it); RFT = middle (own data, reward filter, no RL instability); GRPO = most powerful/expensive (push beyond both). A defensible stack: distill first → RFT to self-improve → GRPO only if RFT plateaus and budget remains. Each stage optional; many production reasoners stop at distillation.
Hybrid models (Qwen3) can toggle thinking on or off per request from the SAME weights — controlled by a control token / system instruction, not a separate model — avoiding the always-on latency tax of a reasoning model that always emits a long