2 min readfrom Machine Learning

DeepSeek V4 paper full version is out, FP4 QAT details and stability tricks [D]

Our take

This week, DeepSeek released the full version of their V4 paper, expanding on the technical insights previewed in April. Notably, the introduction of FP4 quantization-aware training (QAT) during late-stage training significantly enhances performance, achieving a 2x speedup on the QK selector while preserving 99.7% recall. The paper also addresses training stability with innovative mechanisms like anticipatory routing and SwiGLU clamping. Additionally, the generative reward model streamlines evaluations with minimal human labeling. Explore the detailed findings to understand how these advancements could reshape your data management

DeepSeek's V4 technical paper arrives at a pivotal moment for AI development, offering concrete evidence that efficiency gains need not come at the expense of capability. The introduction of FP4 quantization aware training represents a significant shift in how we think about model deployment, particularly when compared to earlier approaches like the 4-bit optimizations we explored with Chaperone-Thinking-LQ-1.0. This technique enables direct inference on FP4 weights while maintaining 99.7% recall on critical selection operations, effectively doubling computational throughput without meaningful quality degradation. For practitioners managing multi-agent systems where individual tasks spawn numerous model calls, these improvements compound dramatically, transforming what was once computationally prohibitive into routine execution.

The efficiency table tells a compelling story that extends beyond raw numbers. V4-Pro achieves just 27% of baseline FLOPs while reducing KV cache requirements to 10% of the V3.2 baseline, and V4-Flash pushes this further to 10% and 7% respectively. These aren't marginal improvements but fundamental restructurings of resource allocation that make large context windows genuinely practical for everyday applications. When we consider that our previous work with 4-bit quantization already demonstrated substantial memory savings, the FP4 approach suggests we're approaching a tipping point where high-performance models become accessible on modest hardware configurations.

Beyond computational efficiency, DeepSeek addresses the elephant in the room for trillion-parameter mixture-of-experts models: training instability. The documentation of anticipatory routing and SwiGLU clamping provides valuable insights for the broader research community grappling with similar divergence problems. Rather than treating these as proprietary secrets, the team shares concrete mechanisms—deliberately desynchronizing router updates and imposing hard limits on activation ranges—that others can adapt and refine. This transparency accelerates collective progress while establishing new baselines for robust MoE training. The generative reward model approach further streamlines development by unifying generation and evaluation within a single framework, reducing the traditional dependency on extensive human labeling while maintaining grounded reasoning capabilities.

Human evaluation results validate that these technical improvements translate to real-world utility. The 62.7% win rate against Gemini 3.1 Pro in Chinese writing tasks, combined with strong performance across white-collar professional tasks, suggests we're witnessing genuine capability advancement rather than benchmark-specific optimization. Perhaps most telling is the coding agent evaluation where 91% of users expressed confidence in V4-Pro as their default coding model—numbers that align with my own experience integrating these models into daily workflows. The question moving forward isn't whether FP4 quantization scales, but how quickly these efficiency gains propagate across the ecosystem and what new applications emerge when computational constraints shift from limiting factors to enablers.

DeepSeek dropped the full V4 paper this week. preview from april was 58 pages, this version adds a lot of technical depth.

What stood out for me.

FP4 quantization aware training. theyre running FP4 QAT directly in late stage training. MoE expert weights quantized to FP4 (the main gpu memory consumer). QK path in the CSA indexer uses FP4 activations. 2x speedup on QK selector with 99.7% recall preserved. inference runs directly on the FP4 weights.

Efficiency table is striking:

Model 1M context FLOPs KV cache
V3.2 baseline baseline
V4-Pro 27% of baseline 10% of baseline
V4-Flash 10% of baseline 7% of baseline

Training stability, two mechanisms.

Trillion parameter MoE has the loss spike problem, divergence, unpredictable failures. they documented two fixes.

Anticipatory routing. they deliberately desync main model and router updates. current step uses latest params for features, but routing uses cached older params. breaks the feedback loop that amplifies anomalies. 20% overhead but only kicks in during loss spikes.

SwiGLU clamping. hard limits on the SwiGLU linear path (-10 to 10) and gate path (max 10). suppresses extreme values that would cascade.

Generative reward model. instead of separate reward models for RLHF, they use the same model to generate and evaluate. trained on scored data, model learns to judge its own outputs with reasoning attached. minimal human labeling, reasoning grounded eval, unified training.

Human eval results. chinese writing, V4-Pro 62.7% win rate vs gemini 3.1 pro, 77.5% on writing quality specifically. white collar tasks (30 advanced tasks across 13 industries), V4-Pro-Max gets 63% non loss rate vs opus 4.6 max. coding agent eval, 52% of users said V4-Pro is ready as their default coding model, 39% leaned yes, less than 9% said no. tracks my own use, swapped V4-Pro into my verdent runs last week and havent noticed a quality hit on day to day work.

The headline for me is FP4 QAT with minimal quality degradation. if this generalizes the cost structure of training and inference shifts a lot, especially noticeable on multi agent setups where one task can spawn 5-10 model calls.

Paper link in comments.

submitted by /u/Dramatic_Spirit_8436
[link] [comments]

Read on the original site

Open the publisher's page for the full experience

View original article

Related Articles