๐จ ๐ ๐๐จ๐ฆ๐ง ๐๐๐๐๐๐ฉ๐๐ ๐ฆ๐ข๐ ๐๐ง๐๐๐ก๐ ๐๐ก๐๐ฅ๐๐๐๐๐๐ ๐ข๐ก ๐ข๐ก๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐! ๐งช๐ฅ
With the support of @AWERXAI, I'm excited to release something VERY special for the local AI community!
๐ง @deepseek_ai ๐๐ฒ๐ฒ๐ฝ๐ฆ๐ฒ๐ฒ๐ธ ๐ฉ๐ฐ.๐ญ ๐๐น๐ฎ๐๐ต ๐ญ๐ฌ๐ญ๐ณ
๐ฆ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ ๐ฎ๐ ๐ท๐๐๐ ๐ญ.๐ฒ๐ฎ ๐ฏ๐ฝ๐ ๐ฒ๐
๐ฝ๐ฒ๐ฟ๐๐
๐ป ๐ต๐ต.๐ฒ๐ญ% ๐๐ข๐๐ ๐ฎ๐ป๐๐๐ฒ๐ฟ-๐๐ผ๐ธ๐ฒ๐ป ๐ฎ๐ด๐ฟ๐ฒ๐ฒ๐บ๐ฒ๐ป๐!
โก ๐ฏ๐ฑ.๐ฑ ๐๐ผ๐ธ/๐ ๐ฑ๐ฒ๐ฐ๐ผ๐ฑ๐ฒ ๐ผ๐ป ๐๐๐๐ !
๐ ๐ญ,๐ญ๐ด๐ต ๐๐ผ๐ธ/๐ ๐ ๐๐ซ ๐ฃ๐ฅ๐๐๐๐๐!
๐ง ๐ฎ๐ฎ๐ต๐ ๐๐ง๐ซ (๐๐๐ถ๐น๐น ๐๐ผ๐ฟ๐ธ๐ถ๐ป๐ด ๐๐ผ ๐ฝ๐๐๐ต ๐ถ๐ ๐ณ๐๐ฟ๐๐ต๐ฒ๐ฟ!)
๐๐๐ ๐ข๐ก ๐ข๐ก๐. ๐๐๐ซ. ๐ฆ๐ฃ๐๐ฅ๐. ๐คฏ
And YES, the quantized weights are AVAILABLE NOW! ๐
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ง๐๐ ๐๐๐ฆ๐ง ๐ณ๐ฎ ๐๐ข๐จ๐ฅ๐ฆ ๐๐๐ฉ๐ ๐๐๐๐ก ๐๐ก๐ฆ๐๐ก๐!
Just a few days ago, I published my article about @nvidiaai's FP4-Local format: The Good, The Bad & The Ugly.
One thing really stuck with me...
NVIDIA demonstrated what was possible when aggressive quantization and intelligent optimization come together.
But there's a problem.
๐ฅ๐๐ฃ๐ฅ๐ข๐๐จ๐๐๐ก๐ ๐ ๐๐ฆ๐ฆ๐๐ฉ๐ ๐ค๐จ๐๐ก๐ง๐๐ญ๐๐ง๐๐ข๐ก ๐ง๐ฅ๐๐๐ก๐๐ก๐ ๐ฃ๐๐ฃ๐๐๐๐ก๐๐ฆ ๐๐ฆ ๐ข๐จ๐ง ๐ข๐ ๐ฅ๐๐๐๐ ๐๐ข๐ฅ ๐ ๐ข๐ฆ๐ง ๐๐ข๐๐๐ ๐๐ ๐๐ก๐ง๐๐จ๐ฆ๐๐๐ฆ๐ง๐ฆ.
That inspired me.
I've been developing my own SAGE-EXL3 process, and I wanted to see just how far I could push the latest DeepSeek Flash release while keeping the results accessible to the community.
So I spent the last 72 hours pushing the limits.
And the results genuinely surprised me! ๐ฅ
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ง๐๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ ๐๐ฅ๐ ๐๐ฅ๐๐ญ๐ฌ!
I measured my 1.62 bpw expert quant against DeepSeek's native FP4 release checkpoint using held-out sequences and full-vocabulary token predictions.
And when I saw the CODE results, I could barely believe it!
๐งช ๐๐๐๐๐๐๐ง๐ฌ ๐ฉ๐ฆ ๐๐๐๐ฃ๐ฆ๐๐๐'๐ฆ ๐ก๐๐ง๐๐ฉ๐ ๐๐ฃ๐ด/๐๐ฃ๐ฐ ๐ฅ๐๐๐๐๐ฆ๐
๐ป ๐๐ข๐๐ โ ๐๐๐บ๐ฎ๐ป๐๐๐ฎ๐น
โ
99.08% Top-1 Agreement
โ
๐ต๐ต.๐ฒ๐ญ% ๐๐ก๐ฆ๐ช๐๐ฅ-๐ข๐ก๐๐ฌ ๐๐๐ฅ๐๐๐ ๐๐ก๐ง!
โ
KL Divergence: 0.0186
๐ง ๐ฅ๐๐๐ฆ๐ข๐ก๐๐ก๐ โ ๐ ๐๐ง๐-๐ฑ๐ฌ๐ฌ
โ
96.04% Top-1 Agreement
โ
97.98% Answer-Only Agreement
โ
KL Divergence: 0.0349
๐ข ๐ ๐๐ง๐ โ ๐๐ฆ๐ ๐ด๐
โ
95.56% Top-1 Agreement
โ
94.19% Answer-Only Agreement
โ
KL Divergence: 0.0477
๐ ๐ข๐ฉ๐๐ฅ๐๐๐ ๐๐๐๐-๐ข๐จ๐ง ๐๐๐๐๐๐๐ง๐ฌ
๐ 94.52% Top-1 Agreement
๐ Mean KL: 0.0982
๐ฏ Median KL: 0.00019
๐ก๐๐๐ฅ-๐๐ข๐ฆ๐ฆ๐๐๐ฆ๐ฆ ๐๐ข๐๐ ๐ง๐ข๐๐๐ก ๐๐๐๐๐๐๐ง๐ฌ ๐๐ง ๐๐จ๐ฆ๐ง ๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ! ๐คฏ
These are direct teacher-forced fidelity measurements against native FP8, not task-level pass rates.
But seeing this level of agreement at such aggressive compression is EXACTLY what I was working toward!
โโโโโโโโโโโโโโโโโโโโ
โก ๐๐ก๐ ๐ฌ๐๐ฆ, ๐๐ง ๐๐๐ง๐จ๐๐๐๐ฌ ๐ฅ๐จ๐ก๐ฆ ๐ข๐ก ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐!
Not two Sparks.
Not four Sparks.
Not an expensive rented GPU cluster.
๐ข๐ก๐ ๐ญ๐ฎ๐ด๐๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐.
My latest vLLM measurements:
โก Decode: 35.5 tok/s
๐ Maximum measured prefill: 1,189 tok/s
For a model this large, compressed this aggressively, and maintaining this level of fidelity...
๐ง๐๐๐ง'๐ฆ ๐ ๐๐๐ ๐๐๐๐ ๐๐ข๐ฅ ๐๐ข๐๐๐ ๐๐! ๐
And remember, 1.62 bpw refers to the routed experts, not every parameter in the full model.
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ช๐๐ฌ ๐ง๐๐๐ฆ ๐ ๐๐ง๐ง๐๐ฅ๐ฆ.
I have a simple goal.
๐ ๐๐๐ ๐ฃ๐ข๐ช๐๐ฅ๐๐จ๐ ๐๐ ๐๐๐๐๐ฆ๐ฆ๐๐๐๐ ๐ง๐ข ๐ฃ๐๐ข๐ฃ๐๐ ๐ช๐๐ข ๐๐ข๐ก'๐ง ๐๐๐ฉ๐ ๐๐๐๐๐ฆ๐ฆ ๐ง๐ข ๐๐๐ง๐๐๐๐ก๐ง๐๐ฅ๐ฆ.
I don't want the future of local AI to be determined by who can rent the most GPUs or afford the largest training runs.
I want developers, independent researchers and enthusiasts to have the freedom to experiment, quantize, optimize and run powerful models on hardware they actually OWN.
NVIDIA's FP4-Local research showed me just how much potential remains in aggressive quantization.
My goal with SAGE-EXL3 is to keep pushing that frontier while making advanced quantization more practical for the wider community.
Today, I'm sharing the quantized checkpoint and the one-Spark serving recipe.
๐ง๐๐๐ฆ ๐๐ฆ ๐๐จ๐ฆ๐ง ๐ง๐๐ ๐๐๐๐๐ก๐ก๐๐ก๐.
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ก๐ข๐ช ๐๐ข๐ฅ ๐ง๐๐ ๐ฅ๐๐๐ ๐ง๐๐ฆ๐ง!
The token-level fidelity results are incredible, but I'm not stopping there.
I'm currently running a broader evaluation campaign to measure how closely this quant preserves the native FP8 model's actual task performance.
๐ป HumanEval+ / MBPP+
๐ง MMLU-Pro STEM / MATH-500
๐ฌ SciCode / LiveCodeBench
๐ง BFCL / Multi-step tool chains
๐ MGSM
๐ง๐๐ ๐๐ข๐๐ ๐๐ฆ ๐ง๐ข ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ง๐๐๐ง ๐๐๐๐ฅ๐๐ฆ๐ฆ๐๐ฉ๐ ๐๐ข๐ ๐ฃ๐ฅ๐๐ฆ๐ฆ๐๐ข๐ก ๐๐ข๐๐ฆ๐ก'๐ง ๐๐๐ฉ๐ ๐ง๐ข ๐ ๐๐๐ก ๐๐๐๐ฅ๐๐ฆ๐ฆ๐๐ฉ๐ ๐ค๐จ๐๐๐๐ง๐ฌ ๐๐ข๐ฆ๐ฆ!
Those task-level results are coming next! ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐๐ก๐ ๐ข๐ก๐ ๐๐๐ง๐ง๐๐ ๐ง๐๐๐ฆ๐๐ฅ...
@mr_r0b0t and I have also been working on an GB10 specialized inference engine called ๐ฅ๐๐ซ๐๐ฏ.
Early testing has been VERY exciting, including 60 tok/s with bursts reaching 74tok/s!
We're putting the finishing touches on it and making sure everything is solid before releasing it.
More on that VERY soon. ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ ๐๐จ๐๐ ๐ง๐๐๐ก๐ ๐ฌ๐ข๐จ!
To @AWERXAI for supporting my work and helping make this contribution to the community possible.
To @nvidiaai for the FP4-Local research that inspired me to push this experiment even further.
To @justinn_builds for his initial vllm TP4 recipe that got me started in the right direction for loading this model up.
To @mr_r0b0t for collaborating with me on what's coming next!
And to @deepseek_ai for continuing to release powerful open-weight models that make community experiments like this possible.
๐ง๐๐ ๐๐๐ฆ๐ง ๐ฃ๐๐ฅ๐ง ๐ข๐ ๐ข๐ฃ๐๐ก ๐๐ ๐๐ฆ ๐ช๐๐๐ง ๐ง๐๐ ๐๐ข๐ ๐ ๐จ๐ก๐๐ง๐ฌ ๐๐๐ก ๐๐จ๐๐๐ ๐ข๐ก ๐ง๐ข๐ฃ ๐ข๐ ๐๐ง. ๐
๐ ๐๐ข๐ช๐ก๐๐ข๐๐ ๐ ๐ฌ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ
huggingface.co/vcruz305/DSV4โฆ
๐ ๏ธ ๐ข๐ก๐-๐ฆ๐ฃ๐๐ฅ๐ ๐ฅ๐๐๐๐ฃ๐
github.com/vcruz305/DSV4.1-Fโฆ
๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐.
๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ.
๐ต๐ต.๐ฒ๐ญ% ๐๐ข๐๐ ๐๐ก๐ฆ๐ช๐๐ฅ ๐๐๐ฅ๐๐๐ ๐๐ก๐ง.
๐๐๐ง'๐ฆ ๐๐๐๐ฃ ๐ฃ๐จ๐ฆ๐๐๐ก๐ ๐๐ข๐๐๐ ๐๐ ๐๐ข๐ฅ๐ช๐๐ฅ๐! ๐๐ฅ
๐จ ๐ ๐๐จ๐ฆ๐ง ๐๐๐๐๐๐ฉ๐๐ ๐ฆ๐ข๐ ๐๐ง๐๐๐ก๐ ๐๐ก๐๐ฅ๐๐๐๐๐๐ ๐ข๐ก ๐ข๐ก๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐! ๐งช๐ฅ
With the support of @AWERXAI, I'm excited to release something VERY special for the local AI community!
๐ง @deepseek_ai ๐๐ฒ๐ฒ๐ฝ๐ฆ๐ฒ๐ฒ๐ธ ๐ฉ๐ฐ.๐ญ ๐๐น๐ฎ๐๐ต ๐ญ๐ฌ๐ญ๐ณ
๐ฆ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ ๐ฎ๐ ๐ท๐๐๐ ๐ญ.๐ฒ๐ฎ ๐ฏ๐ฝ๐ ๐ฒ๐
๐ฝ๐ฒ๐ฟ๐๐
๐ป ๐ต๐ต.๐ฒ๐ญ% ๐๐ข๐๐ ๐ฎ๐ป๐๐๐ฒ๐ฟ-๐๐ผ๐ธ๐ฒ๐ป ๐ฎ๐ด๐ฟ๐ฒ๐ฒ๐บ๐ฒ๐ป๐!
โก ๐ฏ๐ฑ.๐ฑ ๐๐ผ๐ธ/๐ ๐ฑ๐ฒ๐ฐ๐ผ๐ฑ๐ฒ ๐ผ๐ป ๐๐๐๐ !
๐ ๐ญ,๐ญ๐ด๐ต ๐๐ผ๐ธ/๐ ๐ ๐๐ซ ๐ฃ๐ฅ๐๐๐๐๐!
๐ง ๐ฎ๐ฎ๐ต๐ ๐๐ง๐ซ (๐๐๐ถ๐น๐น ๐๐ผ๐ฟ๐ธ๐ถ๐ป๐ด ๐๐ผ ๐ฝ๐๐๐ต ๐ถ๐ ๐ณ๐๐ฟ๐๐ต๐ฒ๐ฟ!)
๐๐๐ ๐ข๐ก ๐ข๐ก๐. ๐๐๐ซ. ๐ฆ๐ฃ๐๐ฅ๐. ๐คฏ
And YES, the quantized weights are AVAILABLE NOW! ๐
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ง๐๐ ๐๐๐ฆ๐ง ๐ณ๐ฎ ๐๐ข๐จ๐ฅ๐ฆ ๐๐๐ฉ๐ ๐๐๐๐ก ๐๐ก๐ฆ๐๐ก๐!
Just a few days ago, I published my article about @nvidiaai's FP4-Local format: The Good, The Bad & The Ugly.
One thing really stuck with me...
NVIDIA demonstrated what was possible when aggressive quantization and intelligent optimization come together.
But there's a problem.
๐ฅ๐๐ฃ๐ฅ๐ข๐๐จ๐๐๐ก๐ ๐ ๐๐ฆ๐ฆ๐๐ฉ๐ ๐ค๐จ๐๐ก๐ง๐๐ญ๐๐ง๐๐ข๐ก ๐ง๐ฅ๐๐๐ก๐๐ก๐ ๐ฃ๐๐ฃ๐๐๐๐ก๐๐ฆ ๐๐ฆ ๐ข๐จ๐ง ๐ข๐ ๐ฅ๐๐๐๐ ๐๐ข๐ฅ ๐ ๐ข๐ฆ๐ง ๐๐ข๐๐๐ ๐๐ ๐๐ก๐ง๐๐จ๐ฆ๐๐๐ฆ๐ง๐ฆ.
That inspired me.
I've been developing my own SAGE-EXL3 process, and I wanted to see just how far I could push the latest DeepSeek Flash release while keeping the results accessible to the community.
So I spent the last 72 hours pushing the limits.
And the results genuinely surprised me! ๐ฅ
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ง๐๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ ๐๐ฅ๐ ๐๐ฅ๐๐ญ๐ฌ!
I measured my 1.62 bpw expert quant against DeepSeek's native FP4 release checkpoint using held-out sequences and full-vocabulary token predictions.
And when I saw the CODE results, I could barely believe it!
๐งช ๐๐๐๐๐๐๐ง๐ฌ ๐ฉ๐ฆ ๐๐๐๐ฃ๐ฆ๐๐๐'๐ฆ ๐ก๐๐ง๐๐ฉ๐ ๐๐ฃ๐ด/๐๐ฃ๐ฐ ๐ฅ๐๐๐๐๐ฆ๐
๐ป ๐๐ข๐๐ โ ๐๐๐บ๐ฎ๐ป๐๐๐ฎ๐น
โ
99.08% Top-1 Agreement
โ
๐ต๐ต.๐ฒ๐ญ% ๐๐ก๐ฆ๐ช๐๐ฅ-๐ข๐ก๐๐ฌ ๐๐๐ฅ๐๐๐ ๐๐ก๐ง!
โ
KL Divergence: 0.0186
๐ง ๐ฅ๐๐๐ฆ๐ข๐ก๐๐ก๐ โ ๐ ๐๐ง๐-๐ฑ๐ฌ๐ฌ
โ
96.04% Top-1 Agreement
โ
97.98% Answer-Only Agreement
โ
KL Divergence: 0.0349
๐ข ๐ ๐๐ง๐ โ ๐๐ฆ๐ ๐ด๐
โ
95.56% Top-1 Agreement
โ
94.19% Answer-Only Agreement
โ
KL Divergence: 0.0477
๐ ๐ข๐ฉ๐๐ฅ๐๐๐ ๐๐๐๐-๐ข๐จ๐ง ๐๐๐๐๐๐๐ง๐ฌ
๐ 94.52% Top-1 Agreement
๐ Mean KL: 0.0982
๐ฏ Median KL: 0.00019
๐ก๐๐๐ฅ-๐๐ข๐ฆ๐ฆ๐๐๐ฆ๐ฆ ๐๐ข๐๐ ๐ง๐ข๐๐๐ก ๐๐๐๐๐๐๐ง๐ฌ ๐๐ง ๐๐จ๐ฆ๐ง ๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ! ๐คฏ
These are direct teacher-forced fidelity measurements against native FP8, not task-level pass rates.
But seeing this level of agreement at such aggressive compression is EXACTLY what I was working toward!
โโโโโโโโโโโโโโโโโโโโ
โก ๐๐ก๐ ๐ฌ๐๐ฆ, ๐๐ง ๐๐๐ง๐จ๐๐๐๐ฌ ๐ฅ๐จ๐ก๐ฆ ๐ข๐ก ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐!
Not two Sparks.
Not four Sparks.
Not an expensive rented GPU cluster.
๐ข๐ก๐ ๐ญ๐ฎ๐ด๐๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐.
My latest vLLM measurements:
โก Decode: 35.5 tok/s
๐ Maximum measured prefill: 1,189 tok/s
For a model this large, compressed this aggressively, and maintaining this level of fidelity...
๐ง๐๐๐ง'๐ฆ ๐ ๐๐๐ ๐๐๐๐ ๐๐ข๐ฅ ๐๐ข๐๐๐ ๐๐! ๐
And remember, 1.62 bpw refers to the routed experts, not every parameter in the full model.
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ช๐๐ฌ ๐ง๐๐๐ฆ ๐ ๐๐ง๐ง๐๐ฅ๐ฆ.
I have a simple goal.
๐ ๐๐๐ ๐ฃ๐ข๐ช๐๐ฅ๐๐จ๐ ๐๐ ๐๐๐๐๐ฆ๐ฆ๐๐๐๐ ๐ง๐ข ๐ฃ๐๐ข๐ฃ๐๐ ๐ช๐๐ข ๐๐ข๐ก'๐ง ๐๐๐ฉ๐ ๐๐๐๐๐ฆ๐ฆ ๐ง๐ข ๐๐๐ง๐๐๐๐ก๐ง๐๐ฅ๐ฆ.
I don't want the future of local AI to be determined by who can rent the most GPUs or afford the largest training runs.
I want developers, independent researchers and enthusiasts to have the freedom to experiment, quantize, optimize and run powerful models on hardware they actually OWN.
NVIDIA's FP4-Local research showed me just how much potential remains in aggressive quantization.
My goal with SAGE-EXL3 is to keep pushing that frontier while making advanced quantization more practical for the wider community.
Today, I'm sharing the quantized checkpoint and the one-Spark serving recipe.
๐ง๐๐๐ฆ ๐๐ฆ ๐๐จ๐ฆ๐ง ๐ง๐๐ ๐๐๐๐๐ก๐ก๐๐ก๐.
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ก๐ข๐ช ๐๐ข๐ฅ ๐ง๐๐ ๐ฅ๐๐๐ ๐ง๐๐ฆ๐ง!
The token-level fidelity results are incredible, but I'm not stopping there.
I'm currently running a broader evaluation campaign to measure how closely this quant preserves the native FP8 model's actual task performance.
๐ป HumanEval+ / MBPP+
๐ง MMLU-Pro STEM / MATH-500
๐ฌ SciCode / LiveCodeBench
๐ง BFCL / Multi-step tool chains
๐ MGSM
๐ง๐๐ ๐๐ข๐๐ ๐๐ฆ ๐ง๐ข ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ง๐๐๐ง ๐๐๐๐ฅ๐๐ฆ๐ฆ๐๐ฉ๐ ๐๐ข๐ ๐ฃ๐ฅ๐๐ฆ๐ฆ๐๐ข๐ก ๐๐ข๐๐ฆ๐ก'๐ง ๐๐๐ฉ๐ ๐ง๐ข ๐ ๐๐๐ก ๐๐๐๐ฅ๐๐ฆ๐ฆ๐๐ฉ๐ ๐ค๐จ๐๐๐๐ง๐ฌ ๐๐ข๐ฆ๐ฆ!
Those task-level results are coming next! ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐๐ก๐ ๐ข๐ก๐ ๐๐๐ง๐ง๐๐ ๐ง๐๐๐ฆ๐๐ฅ...
@mr_r0b0t and I have also been working on an GB10 specialized inference engine called ๐ฅ๐๐ซ๐๐ฏ.
Early testing has been VERY exciting, including 60 tok/s with bursts reaching 74tok/s!
We're putting the finishing touches on it and making sure everything is solid before releasing it.
More on that VERY soon. ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ ๐๐จ๐๐ ๐ง๐๐๐ก๐ ๐ฌ๐ข๐จ!
To @AWERXAI for supporting my work and helping make this contribution to the community possible.
To @nvidiaai for the FP4-Local research that inspired me to push this experiment even further.
To @justinn_builds for his initial vllm TP4 recipe that got me started in the right direction for loading this model up.
To @mr_r0b0t for collaborating with me on what's coming next!
And to @deepseek_ai for continuing to release powerful open-weight models that make community experiments like this possible.
๐ง๐๐ ๐๐๐ฆ๐ง ๐ฃ๐๐ฅ๐ง ๐ข๐ ๐ข๐ฃ๐๐ก ๐๐ ๐๐ฆ ๐ช๐๐๐ง ๐ง๐๐ ๐๐ข๐ ๐ ๐จ๐ก๐๐ง๐ฌ ๐๐๐ก ๐๐จ๐๐๐ ๐ข๐ก ๐ง๐ข๐ฃ ๐ข๐ ๐๐ง. ๐
๐ ๐๐ข๐ช๐ก๐๐ข๐๐ ๐ ๐ฌ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ
huggingface.co/vcruz305/DSV4โฆ
๐ ๏ธ ๐ข๐ก๐-๐ฆ๐ฃ๐๐ฅ๐ ๐ฅ๐๐๐๐ฃ๐
github.com/vcruz305/DSV4.1-Fโฆ
๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐.
๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ.
๐ต๐ต.๐ฒ๐ญ% ๐๐ข๐๐ ๐๐ก๐ฆ๐ช๐๐ฅ ๐๐๐ฅ๐๐๐ ๐๐ก๐ง.
๐๐๐ง'๐ฆ ๐๐๐๐ฃ ๐ฃ๐จ๐ฆ๐๐๐ก๐ ๐๐ข๐๐๐ ๐๐ ๐๐ข๐ฅ๐ช๐๐ฅ๐! ๐๐ฅ
๐จ ๐ ๐๐จ๐ฆ๐ง ๐ฆ๐๐ฅ๐จ๐ก๐ ๐ข๐ฅ๐ก๐๐ง๐ ๐ญ.๐ฑ ๐ญ๐ฎ๐ฎ๐ ๐๐ข๐ฅ ๐ง๐๐ ๐ฐ๐ด๐๐ ๐ฉ๐ฅ๐๐ ๐๐ข๐ ๐ ๐จ๐ก๐๐ง๐ฌ! ๐งช๐ฅ
@ornith_ JUST released their new Ornith-1.5-122B, and naturally, I HAD to see how far I could push it with SAGE-EXL3!
And the results surprised even ME! ๐คฏ
Introducing...
๐ข ๐ข๐ฟ๐ป๐ถ๐๐ต-๐ญ.๐ฑ-๐ญ๐ฎ๐ฎ๐-๐๐ซ๐๐ฏ-๐ฆ๐๐๐-๐ฎ.๐ฑ๐ด๐ฏ๐ฝ๐
๐ฆ ~39.6 GiB GPU-resident LM weights
๐ง 122B-class Mixture-of-Experts model
โก 2.58 bpw routed experts
๐ป Targeting 48GB VRAM GPUs and above!
๐ vLLM + EXL3 inference
๐๐จ๐ง ๐๐๐ฅ๐'๐ฆ ๐ช๐๐๐ฅ๐ ๐๐ง ๐๐๐ง๐ฆ ๐๐ก๐ง๐๐ฅ๐๐ฆ๐ง๐๐ก๐... ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ฆ๐๐๐ ๐ฎ.๐ฑ๐ด ๐๐ฃ๐ช ๐๐ ๐ ๐๐-๐๐๐๐๐ ๐๐๐ค๐๐ญ ๐ฐ.๐ฌ ๐๐ฃ๐ช!
I compared my release against Mia-AiLab's Ornith-1.5-122B-EXL3-EAQv1-4-bpw quantization.
Same model family.
Same DGX Spark.
353 matched benchmark questions.
9 evaluation suites.
Strict pass@1 scoring.
๐ข ๐ ๐ฌ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ ๐ฎ.๐ฑ๐ด ๐๐ฃ๐ช
๐ฆ 41.00 GiB LM weights
๐ ๐ต๐ญ.๐ณ๐ด% โ ๐ฏ๐ฎ๐ฐ/๐ฏ๐ฑ๐ฏ
๐ฃ ๐ ๐๐-๐๐๐๐๐ ๐๐๐ค๐๐ญ ๐ฐ.๐ฌ ๐๐ฃ๐ช
๐ฆ 59.00 GiB LM weights
๐ ๐ต๐ญ.๐ฑ๐ฌ% โ ๐ฏ๐ฎ๐ฏ/๐ฏ๐ฑ๐ฏ
๐๐ฃ๐ฃ๐ฅ๐ข๐ซ๐๐ ๐๐ง๐๐๐ฌ ๐ฏ๐ฌ.๐ฑ% ๐ฆ๐ ๐๐๐๐๐ฅ ๐๐ ๐ช๐๐๐๐๐ง ๐๐ข๐ข๐ง๐ฃ๐ฅ๐๐ก๐ง...
๐๐ก๐ ๐๐ฆ๐ฆ๐๐ก๐ง๐๐๐๐๐ฌ ๐ง๐๐ ๐ฆ๐๐ ๐ ๐ข๐ฉ๐๐ฅ๐๐๐ ๐ค๐จ๐๐๐๐ง๐ฌ! ๐คฏ
Mine finished one question ahead overall. That's effectively a tie at this sample size, but the coding breakdown is particularly interesting!
โโโโโโโโโโโโโโโโโโโโ
๐ป ๐๐ข๐๐๐ก๐ ๐๐ฆ ๐ช๐๐๐ฅ๐ ๐ฆ๐๐๐ ๐ฃ๐จ๐๐๐ฆ ๐๐๐๐๐!
Scores shown as SAGE โ Mia:
โ
HumanEval+: 39/40 โ 39/40
๐ MBPP+: 53/60 โ 51/60
๐ LiveCodeBench: 15/20 โ 14/20
๐ SciCode: 5/10 โ 4/10
๐๐ข๐๐๐ก๐ ๐ฆ๐จ๐๐ง๐ข๐ง๐๐:
๐ข SAGE: 112/130 โ 86.15%
๐ฃ Mia: 108/130 โ 83.08%
๐๐ข๐จ๐ฅ ๐ ๐ข๐ฅ๐ ๐๐ข๐๐๐ก๐ ๐ค๐จ๐๐ฆ๐ง๐๐ข๐ก๐ฆ ๐ฃ๐๐ฆ๐ฆ๐๐ ๐ช๐๐ง๐ ๐ฏ๐ฌ.๐ฑ% ๐๐๐ฆ๐ฆ ๐ ๐ข๐๐๐-๐ช๐๐๐๐๐ง ๐ ๐๐ ๐ข๐ฅ๐ฌ! ๐ฅ
For transparency, Mia scored higher on MMLU-Pro STEM (96 vs 94) and MATH-500 (39 vs 38). Both tied on HumanEval+, MGSM, BFCL and multi-step tool chains.
This isn't about claiming one quant wins everything.
๐๐ง'๐ฆ ๐๐๐ข๐จ๐ง ๐๐๐ง๐ง๐๐ก๐ ๐ ๐ข๐ฅ๐ ๐ค๐จ๐๐๐๐ง๐ฌ ๐ฃ๐๐ฅ ๐๐.
โโโโโโโโโโโโโโโโโโโโ
โก ๐๐ก๐ ๐ฌ๐๐ฆ, ๐๐ง ๐ฅ๐จ๐ก๐ฆ ๐ข๐ก ๐๐๐๐ !
My measured vLLM 0.32.0 + vllm-exl3 performance on ONE DGX Spark:
โก 30.51 tok/s single-stream decode
๐ 32.60 tok/s with MTP-1 (greedy code test)
๐ฅ 89.21 tok/s aggregate decode @ C8
๐ฅ 1,119 tok/s cold prefill (2K prompt)
๐ง Native 262K context support
The public recipe is being streamlined around vLLM, with the older alternative serving instructions being retired.
My goal is to make this practical for people who want an OpenAI-compatible local endpoint without needing an 80GB+ GPU just to load the model.
The 48GB tier is the intended target; these published performance measurements were performed on my DGX Spark. Actual available context and batching capacity will depend on the GPU.
โโโโโโโโโโโโโโโโโโโโ
๐ ๐๐จ๐ง ๐๐๐ฅ๐'๐ฆ ๐ช๐๐๐ง ๐'๐ ๐ฅ๐๐๐๐๐ฌ ๐๐ซ๐๐๐ง๐๐ ๐๐๐ข๐จ๐ง...
โก ๐ง๐ช๐ข ๐ ๐ข๐๐๐๐ฆ. ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐. ๐๐ฆ ๐๐ข๐ ๐๐ก๐ ๐๐๐๐!
If you've followed my previous experiments, you know I LOVE finding ways to run multiple powerful models on a SINGLE DGX Spark.
And this ~41 GiB Ornith quant opens up some VERY interesting possibilities!
Imagine...
๐ง ๐ค๐ช๐๐ก๐ฏ.๐ด-๐๐๐๐ฆ๐-๐ก๐๐ซ๐ง โ ๐ ๐๐ฆ๐ง๐๐ฅ ๐๐๐๐ก๐ง
A larger lead model handling complex reasoning, planning, orchestration and long-context tasks.
โก ๐ข๐ฅ๐ก๐๐ง๐ ๐ญ.๐ฑ ๐ญ๐ฎ๐ฎ๐ โ ๐ฆ๐จ๐-๐๐๐๐ก๐ง
My compact SAGE-EXL3 handling delegated coding, tool use and specialized agentic workloads!
๐ง๐ช๐ข ๐ญ๐ฎ๐ฌ๐+ ๐๐๐๐ฆ๐ฆ ๐ ๐ข๐๐๐๐ฆ.
๐ข๐ก๐ ๐ญ๐ฎ๐ด๐๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐.
๐๐จ๐๐๐ฌ ๐๐ข๐๐๐! ๐คฏ
That's the direction I'm exploring for my NEXT Two Models. One Spark. experiment!
Of course, simultaneous residency, runtime overhead, KV-cache allocation and actual master-worker performance still need validation with the selected Qwen quantization.
But the smaller we can make these models without sacrificing useful quality, the MORE possibilities we unlock!
๐ง๐๐๐ฆ ๐๐ฆ ๐ช๐๐ฌ ๐ ๐๐ข ๐ช๐๐๐ง ๐ ๐๐ข! ๐
โโโโโโโโโโโโโโโโโโโโ
๐ฌ ๐ข๐ก๐ ๐๐๐ง๐ง๐๐ ๐ฅ๐๐ซ๐๐ฏ ๐ง๐๐๐ฆ๐๐ฅ...
In separate development testing, REXL3 has also reached:
โก 90.82 tok/s aggregate @ C8
๐ ~2,150 tok/s prefill
More on that another time. ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ ๐๐๐๐ก๐ ๐๐ฅ๐ข๐ก๐ง๐๐๐ฅ ๐๐ ๐๐๐๐๐ฆ๐ฆ๐๐๐๐!
Not everyone has a DGX Spark or an 80GB GPU.
But a LOT of enthusiasts, developers and independent researchers have access to 48GB-class hardware.
I want powerful open-weight models to be accessible to MORE of those people.
And beyond just fitting one model, I want to show what's possible when we start combining them on the SAME hardware!
Huge thanks to @ornith_ for releasing Ornith-1.5-122B under an open-weight license and continuing to push efficient AI models forward!
โโโโโโโโโโโโโโโโโโโโ
๐ ๐๐ข๐ช๐ก๐๐ข๐๐ ๐ ๐ฌ ๐๐ซ๐๐ฏ
huggingface.co/vcruz305/Orniโฆ
๐ ๏ธ ๐ฉ๐๐๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐ ๐ฅ๐๐๐๐ฃ๐
github.com/vcruz305/Ornith-1โฆ
๐ฆ๐ ๐๐๐๐๐ฅ ๐ช๐๐๐๐๐ง๐ฆ. ๐๐๐๐๐๐ฅ ๐ฃ๐ข๐ฆ๐ฆ๐๐๐๐๐๐ง๐๐๐ฆ.
๐ง๐ช๐ข ๐ ๐ข๐๐๐๐ฆ. ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐. โก
๐๐๐ง'๐ฆ ๐๐๐๐ฃ ๐ฃ๐จ๐ฆ๐๐๐ก๐ ๐๐ข๐๐๐ ๐๐ ๐๐ข๐ฅ๐ช๐๐ฅ๐! ๐๐ฅ
๐จ ๐ง๐ช๐ข ๐ก๐๐ช ๐๐๐๐ฃ๐ฆ๐๐๐ ๐ฉ๐ฐ.๐ญ ๐๐๐๐ฆ๐ ๐ฅ๐๐๐๐๐ฆ๐๐ฆ! ๐ก๏ธ๐ฅ
Iโm excited to share TWO alternate DERISKED SAGE-EXL3 quantizations for cybersecurity research and security-focused AI workflows! These are the HIGHEST quality EXL3 quants you can find for this Deepseek model!
Built in collaboration with @Blackfrost_AI ๐ฅถโ๏ธ
๐ข 1.61 bpw โ ONE DGX SPARK
โ
94.68% assistant-token top-1 agreement
โ
~112.9 GiB resident footprint
๐ฃ 2.50 bpw โ TWO DGX SPARKS
โ
96.71% assistant-token top-1 agreement
โ
Higher precision for those with more memory - practically lossless ๐
Both measured against DeepSeekโs official FP8/FP4 checkpoint. These are token-fidelity results, not cybersecurity task scores.
๐ ๐ข๐ฅ๐ ๐๐๐ข๐๐๐๐ฆ. ๐ ๐ข๐ฅ๐ ๐๐ข๐๐๐ ๐๐. ๐ ๐ข๐ฅ๐ ๐๐ฅ๐๐๐๐ข๐ ๐ง๐ข ๐๐ซ๐ฃ๐๐ฅ๐๐ ๐๐ก๐ง! ๐
๐ 1.61 bpw โ ONE SPARK
huggingface.co/vcruz305/DSV4โฆ
๐ 2.50 bpw โ TWO SPARKS
huggingface.co/vcruz305/DSV4โฆ
Huge thanks to @Blackfrost_AI for not only making the model, but providing the compute for us to continue collaborating on these releases! ๐๐ฅ
๐จ ๐ ๐๐จ๐ฆ๐ง ๐๐๐๐๐๐ฉ๐๐ ๐ฆ๐ข๐ ๐๐ง๐๐๐ก๐ ๐๐ก๐๐ฅ๐๐๐๐๐๐ ๐ข๐ก ๐ข๐ก๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐! ๐งช๐ฅ
With the support of @AWERXAI, I'm excited to release something VERY special for the local AI community!
๐ง @deepseek_ai ๐๐ฒ๐ฒ๐ฝ๐ฆ๐ฒ๐ฒ๐ธ ๐ฉ๐ฐ.๐ญ ๐๐น๐ฎ๐๐ต ๐ญ๐ฌ๐ญ๐ณ
๐ฆ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ ๐ฎ๐ ๐ท๐๐๐ ๐ญ.๐ฒ๐ฎ ๐ฏ๐ฝ๐ ๐ฒ๐
๐ฝ๐ฒ๐ฟ๐๐
๐ป ๐ต๐ต.๐ฒ๐ญ% ๐๐ข๐๐ ๐ฎ๐ป๐๐๐ฒ๐ฟ-๐๐ผ๐ธ๐ฒ๐ป ๐ฎ๐ด๐ฟ๐ฒ๐ฒ๐บ๐ฒ๐ป๐!
โก ๐ฏ๐ฑ.๐ฑ ๐๐ผ๐ธ/๐ ๐ฑ๐ฒ๐ฐ๐ผ๐ฑ๐ฒ ๐ผ๐ป ๐๐๐๐ !
๐ ๐ญ,๐ญ๐ด๐ต ๐๐ผ๐ธ/๐ ๐ ๐๐ซ ๐ฃ๐ฅ๐๐๐๐๐!
๐ง ๐ฎ๐ฎ๐ต๐ ๐๐ง๐ซ (๐๐๐ถ๐น๐น ๐๐ผ๐ฟ๐ธ๐ถ๐ป๐ด ๐๐ผ ๐ฝ๐๐๐ต ๐ถ๐ ๐ณ๐๐ฟ๐๐ต๐ฒ๐ฟ!)
๐๐๐ ๐ข๐ก ๐ข๐ก๐. ๐๐๐ซ. ๐ฆ๐ฃ๐๐ฅ๐. ๐คฏ
And YES, the quantized weights are AVAILABLE NOW! ๐
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ง๐๐ ๐๐๐ฆ๐ง ๐ณ๐ฎ ๐๐ข๐จ๐ฅ๐ฆ ๐๐๐ฉ๐ ๐๐๐๐ก ๐๐ก๐ฆ๐๐ก๐!
Just a few days ago, I published my article about @nvidiaai's FP4-Local format: The Good, The Bad & The Ugly.
One thing really stuck with me...
NVIDIA demonstrated what was possible when aggressive quantization and intelligent optimization come together.
But there's a problem.
๐ฅ๐๐ฃ๐ฅ๐ข๐๐จ๐๐๐ก๐ ๐ ๐๐ฆ๐ฆ๐๐ฉ๐ ๐ค๐จ๐๐ก๐ง๐๐ญ๐๐ง๐๐ข๐ก ๐ง๐ฅ๐๐๐ก๐๐ก๐ ๐ฃ๐๐ฃ๐๐๐๐ก๐๐ฆ ๐๐ฆ ๐ข๐จ๐ง ๐ข๐ ๐ฅ๐๐๐๐ ๐๐ข๐ฅ ๐ ๐ข๐ฆ๐ง ๐๐ข๐๐๐ ๐๐ ๐๐ก๐ง๐๐จ๐ฆ๐๐๐ฆ๐ง๐ฆ.
That inspired me.
I've been developing my own SAGE-EXL3 process, and I wanted to see just how far I could push the latest DeepSeek Flash release while keeping the results accessible to the community.
So I spent the last 72 hours pushing the limits.
And the results genuinely surprised me! ๐ฅ
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ง๐๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ ๐๐ฅ๐ ๐๐ฅ๐๐ญ๐ฌ!
I measured my 1.62 bpw expert quant against DeepSeek's native FP4 release checkpoint using held-out sequences and full-vocabulary token predictions.
And when I saw the CODE results, I could barely believe it!
๐งช ๐๐๐๐๐๐๐ง๐ฌ ๐ฉ๐ฆ ๐๐๐๐ฃ๐ฆ๐๐๐'๐ฆ ๐ก๐๐ง๐๐ฉ๐ ๐๐ฃ๐ด/๐๐ฃ๐ฐ ๐ฅ๐๐๐๐๐ฆ๐
๐ป ๐๐ข๐๐ โ ๐๐๐บ๐ฎ๐ป๐๐๐ฎ๐น
โ
99.08% Top-1 Agreement
โ
๐ต๐ต.๐ฒ๐ญ% ๐๐ก๐ฆ๐ช๐๐ฅ-๐ข๐ก๐๐ฌ ๐๐๐ฅ๐๐๐ ๐๐ก๐ง!
โ
KL Divergence: 0.0186
๐ง ๐ฅ๐๐๐ฆ๐ข๐ก๐๐ก๐ โ ๐ ๐๐ง๐-๐ฑ๐ฌ๐ฌ
โ
96.04% Top-1 Agreement
โ
97.98% Answer-Only Agreement
โ
KL Divergence: 0.0349
๐ข ๐ ๐๐ง๐ โ ๐๐ฆ๐ ๐ด๐
โ
95.56% Top-1 Agreement
โ
94.19% Answer-Only Agreement
โ
KL Divergence: 0.0477
๐ ๐ข๐ฉ๐๐ฅ๐๐๐ ๐๐๐๐-๐ข๐จ๐ง ๐๐๐๐๐๐๐ง๐ฌ
๐ 94.52% Top-1 Agreement
๐ Mean KL: 0.0982
๐ฏ Median KL: 0.00019
๐ก๐๐๐ฅ-๐๐ข๐ฆ๐ฆ๐๐๐ฆ๐ฆ ๐๐ข๐๐ ๐ง๐ข๐๐๐ก ๐๐๐๐๐๐๐ง๐ฌ ๐๐ง ๐๐จ๐ฆ๐ง ๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ! ๐คฏ
These are direct teacher-forced fidelity measurements against native FP8, not task-level pass rates.
But seeing this level of agreement at such aggressive compression is EXACTLY what I was working toward!
โโโโโโโโโโโโโโโโโโโโ
โก ๐๐ก๐ ๐ฌ๐๐ฆ, ๐๐ง ๐๐๐ง๐จ๐๐๐๐ฌ ๐ฅ๐จ๐ก๐ฆ ๐ข๐ก ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐!
Not two Sparks.
Not four Sparks.
Not an expensive rented GPU cluster.
๐ข๐ก๐ ๐ญ๐ฎ๐ด๐๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐.
My latest vLLM measurements:
โก Decode: 35.5 tok/s
๐ Maximum measured prefill: 1,189 tok/s
For a model this large, compressed this aggressively, and maintaining this level of fidelity...
๐ง๐๐๐ง'๐ฆ ๐ ๐๐๐ ๐๐๐๐ ๐๐ข๐ฅ ๐๐ข๐๐๐ ๐๐! ๐
And remember, 1.62 bpw refers to the routed experts, not every parameter in the full model.
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ช๐๐ฌ ๐ง๐๐๐ฆ ๐ ๐๐ง๐ง๐๐ฅ๐ฆ.
I have a simple goal.
๐ ๐๐๐ ๐ฃ๐ข๐ช๐๐ฅ๐๐จ๐ ๐๐ ๐๐๐๐๐ฆ๐ฆ๐๐๐๐ ๐ง๐ข ๐ฃ๐๐ข๐ฃ๐๐ ๐ช๐๐ข ๐๐ข๐ก'๐ง ๐๐๐ฉ๐ ๐๐๐๐๐ฆ๐ฆ ๐ง๐ข ๐๐๐ง๐๐๐๐ก๐ง๐๐ฅ๐ฆ.
I don't want the future of local AI to be determined by who can rent the most GPUs or afford the largest training runs.
I want developers, independent researchers and enthusiasts to have the freedom to experiment, quantize, optimize and run powerful models on hardware they actually OWN.
NVIDIA's FP4-Local research showed me just how much potential remains in aggressive quantization.
My goal with SAGE-EXL3 is to keep pushing that frontier while making advanced quantization more practical for the wider community.
Today, I'm sharing the quantized checkpoint and the one-Spark serving recipe.
๐ง๐๐๐ฆ ๐๐ฆ ๐๐จ๐ฆ๐ง ๐ง๐๐ ๐๐๐๐๐ก๐ก๐๐ก๐.
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ก๐ข๐ช ๐๐ข๐ฅ ๐ง๐๐ ๐ฅ๐๐๐ ๐ง๐๐ฆ๐ง!
The token-level fidelity results are incredible, but I'm not stopping there.
I'm currently running a broader evaluation campaign to measure how closely this quant preserves the native FP8 model's actual task performance.
๐ป HumanEval+ / MBPP+
๐ง MMLU-Pro STEM / MATH-500
๐ฌ SciCode / LiveCodeBench
๐ง BFCL / Multi-step tool chains
๐ MGSM
๐ง๐๐ ๐๐ข๐๐ ๐๐ฆ ๐ง๐ข ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ง๐๐๐ง ๐๐๐๐ฅ๐๐ฆ๐ฆ๐๐ฉ๐ ๐๐ข๐ ๐ฃ๐ฅ๐๐ฆ๐ฆ๐๐ข๐ก ๐๐ข๐๐ฆ๐ก'๐ง ๐๐๐ฉ๐ ๐ง๐ข ๐ ๐๐๐ก ๐๐๐๐ฅ๐๐ฆ๐ฆ๐๐ฉ๐ ๐ค๐จ๐๐๐๐ง๐ฌ ๐๐ข๐ฆ๐ฆ!
Those task-level results are coming next! ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐๐ก๐ ๐ข๐ก๐ ๐๐๐ง๐ง๐๐ ๐ง๐๐๐ฆ๐๐ฅ...
@mr_r0b0t and I have also been working on an GB10 specialized inference engine called ๐ฅ๐๐ซ๐๐ฏ.
Early testing has been VERY exciting, including 60 tok/s with bursts reaching 74tok/s!
We're putting the finishing touches on it and making sure everything is solid before releasing it.
More on that VERY soon. ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ ๐๐จ๐๐ ๐ง๐๐๐ก๐ ๐ฌ๐ข๐จ!
To @AWERXAI for supporting my work and helping make this contribution to the community possible.
To @nvidiaai for the FP4-Local research that inspired me to push this experiment even further.
To @justinn_builds for his initial vllm TP4 recipe that got me started in the right direction for loading this model up.
To @mr_r0b0t for collaborating with me on what's coming next!
And to @deepseek_ai for continuing to release powerful open-weight models that make community experiments like this possible.
๐ง๐๐ ๐๐๐ฆ๐ง ๐ฃ๐๐ฅ๐ง ๐ข๐ ๐ข๐ฃ๐๐ก ๐๐ ๐๐ฆ ๐ช๐๐๐ง ๐ง๐๐ ๐๐ข๐ ๐ ๐จ๐ก๐๐ง๐ฌ ๐๐๐ก ๐๐จ๐๐๐ ๐ข๐ก ๐ง๐ข๐ฃ ๐ข๐ ๐๐ง. ๐
๐ ๐๐ข๐ช๐ก๐๐ข๐๐ ๐ ๐ฌ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ
huggingface.co/vcruz305/DSV4โฆ
๐ ๏ธ ๐ข๐ก๐-๐ฆ๐ฃ๐๐ฅ๐ ๐ฅ๐๐๐๐ฃ๐
github.com/vcruz305/DSV4.1-Fโฆ
๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐.
๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ.
๐ต๐ต.๐ฒ๐ญ% ๐๐ข๐๐ ๐๐ก๐ฆ๐ช๐๐ฅ ๐๐๐ฅ๐๐๐ ๐๐ก๐ง.
๐๐๐ง'๐ฆ ๐๐๐๐ฃ ๐ฃ๐จ๐ฆ๐๐๐ก๐ ๐๐ข๐๐๐ ๐๐ ๐๐ข๐ฅ๐ช๐๐ฅ๐! ๐๐ฅ
๐จ ๐ ๐ฌ ๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐๐๐ฃ๐ฆ๐๐๐ ๐ค๐จ๐๐ก๐ง ๐๐จ๐ฆ๐ง ๐๐๐๐ง ๐ง๐ช๐ข ๐๐๐๐๐๐ฅ-๐ฃ๐ฅ๐๐๐๐ฆ๐๐ข๐ก, ๐ง๐ช๐ข-๐ฆ๐ฃ๐๐ฅ๐ ๐ค๐จ๐๐ก๐ง๐ฆ! ๐งช๐ฅ
And I have the REAL benchmark results to prove it! ๐คฏ
Remember my DeepSeek V4.1 Flash 1017 SAGE-EXL3 release from YESTERDAY?
๐ฆ 1.62 bpw routed experts
๐ป 99.61% code answer-token agreement
๐ฅ๏ธ ONE DGX Spark @nvidiaai
Well, I promised to go beyond KL divergence and token agreement and test ACTUAL coding, mathematics, reasoning and tool execution.
๐ง๐๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ ๐๐ฅ๐ ๐๐ก!
โโโโโโโโโโโโโโโโโโโโ
๐ ๐๐๐๐ฃ๐ฆ๐๐๐ ๐ฉ๐ฐ.๐ญ ๐๐๐๐ฆ๐ ๐ญ๐ฌ๐ญ๐ณ โ ๐ก๐๐ก๐-๐ฆ๐จ๐๐ง๐ ๐ฆ๐๐ข๐ช๐๐ข๐ช๐ก
353 matched benchmark questions.
9 evaluation suites.
Strict pass@1 scoring.
Temperature 0.
๐ข ๐ ๐ฌ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ โ ๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช
๐ฅ๏ธ 1ร DGX Spark
๐ ๐ต๐ฐ.๐ญ% โ ๐ฏ๐ฏ๐ฎ/๐ฏ๐ฑ๐ฏ ๐ฃ๐๐ฆ๐ฆ๐๐!
๐ต ๐๐ ๐ก๐๐ช โ ๐ฎ.๐ด ๐๐ฃ๐ช
๐ฅ๏ธ 2ร DGX Sparks
๐ 90.1% โ 318/353
๐ฃ ๐ ๐๐๐๐๐ โ ๐ฎ.๐ต ๐๐ฃ๐ช
๐ฅ๏ธ 2ร DGX Sparks
๐ 88.4% โ 312/353
๐'๐ ๐จ๐ฆ๐๐ก๐ ๐ฐ๐ฎโ๐ฐ๐ฐ% ๐๐๐ช๐๐ฅ ๐๐๐ง๐ฆ ๐ฃ๐๐ฅ ๐ฅ๐ข๐จ๐ง๐๐ ๐๐ซ๐ฃ๐๐ฅ๐ง ๐ฃ๐๐ฅ๐๐ ๐๐ง๐๐ฅ...
๐๐ก๐ ๐ฆ๐๐ข๐ฅ๐๐ก๐ ๐๐๐๐๐๐ฅ ๐ข๐ก ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐! ๐คฏ
โโโโโโโโโโโโโโโโโโโโ
๐ป ๐ง๐๐ ๐๐ข๐๐๐ก๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ ๐๐ฅ๐ ๐๐ก๐๐ฅ๐๐๐๐๐๐!
Scores shown as SAGE / JJ / Mia:
๐ HumanEval+
39/40 vs 34/40 vs 34/40
๐ MBPP+
53/60 vs 50/60 vs 49/60
๐ LiveCodeBench
15/17 vs 14/17 vs 11/17
๐ง ๐ฅ๐๐๐ฆ๐ข๐ก๐๐ก๐ & ๐ ๐๐ง๐
๐ MMLU-Pro STEM
95/100 vs 93/100 vs 91/100
๐ MATH-500
40/40 vs 36/40 vs 36/40
๐๐๐ฉ๐ ๐ข๐จ๐ง๐ฅ๐๐๐๐ง ๐ช๐๐ก๐ฆ! ๐ฅ
I also tied both models on:
โ
MGSM: 40/40
โ
BFCL: 39/40
โ
SciCode first-step: 6/10
For full transparency, both JJ and Mia won the multi-step tool-chain test, scoring 6/6 against my 5/6.
๐ฆ๐ข ๐ง๐๐๐ง'๐ฆ ๐ฑ ๐ช๐๐ก๐ฆ, ๐ฏ ๐ง๐๐๐ฆ, ๐๐ก๐ ๐ญ ๐๐ข๐ฆ๐ฆ.
All while using a substantially lower expert bitrate!
โโโโโโโโโโโโโโโโโโโโ
๐ ๐๐๐ ๐จ๐ฃ๐๐๐ง๐: ๐ ๐ฌ ๐ฃ๐จ๐๐๐๐ ๐๐๐๐ ๐ฅ๐๐๐๐ฃ๐ ๐๐ฆ ๐ก๐ข๐ช ๐ฃ๐จ๐ฆ๐๐๐ก๐ ๐ฑ๐ฎ๐ฐ๐ ๐๐ข๐ก๐ง๐๐ซ๐ง!
YES. ON ONE DGX SPARK! ๐คฏ
With the latest W2 kernel, updated expert set and KV-cache configuration, I just completed an actual long-context retrieval test!
๐ ๐๐จ๐๐-๐๐๐ก๐๐ง๐ ๐ฃ๐ฅ๐ข๐ ๐ฃ๐ง ๐ง๐๐ฆ๐ง
๐ง 518,103 INPUT TOKENS!
๐ฏ Fact planted HALFWAY through the context
โ
THE MODEL FOUND THE FACT!
โฑ๏ธ Time to first token: 470 seconds (~7.8 minutes)
๐ Prefill: ~1,100 tok/s
โก Decode at that context depth: 25.6 tok/s
๐พ Minimum available memory: 2.19 GiB
๐ก๏ธ Memory safety floor: 0.5 GiB
And on SHORTER prompts?
โก ~36 TOK/S DECODE!
๐ง ~130.5 ms per speculative step
๐ฏ ~4.7 accepted tokens per step
๐ช๐'๐ฅ๐ ๐ง๐๐๐๐๐ก๐ ๐๐๐ข๐จ๐ง ๐ข๐ฉ๐๐ฅ ๐๐๐๐ ๐ ๐ ๐๐๐๐๐ข๐ก ๐๐ก๐ฃ๐จ๐ง ๐ง๐ข๐๐๐ก๐ฆ ๐ฃ๐ฅ๐ข๐๐๐ฆ๐ฆ๐๐ ๐ข๐ก ๐ ๐ฆ๐๐ก๐๐๐ ๐ฆ๐ฃ๐๐ฅ๐! ๐ฅ
To be clear, this was a successful full-length retrieval test, not a claim of perfect accuracy across every possible long-context task.
And the 7.8-minute prefill is a real trade-off at that depth.
But seeing a model this large, with this level of compression, successfully retrieve information buried inside 518K tokens on ONE 128GB machine is an exciting milestone for local AI!
โโโโโโโโโโโโโโโโโโโโ
โก ๐๐ก๐ ๐ง๐๐ ๐ข๐ก๐-๐ฆ๐ฃ๐๐ฅ๐ ๐ฃ๐๐ฅ๐๐ข๐ฅ๐ ๐๐ก๐๐ ๐๐๐๐ฃ๐ฆ ๐๐ ๐ฃ๐ฅ๐ข๐ฉ๐๐ก๐!
Separately, my latest REXL3 development measurements at a 256K context configuration:
โก 55.35 tok/s single-stream decode
๐ 2,045 tok/s peak prefill
โฑ๏ธ 509 ms TTFT on a 512-token prompt
Those REXL3 numbers come from a different engine and workload than the new public vLLM 518K-token test.
And here's something else I'm particularly excited about...
๐๐๐ ๐ญ๐ฑ,๐ฏ๐ฒ๐ฌ ๐ฅ๐ข๐จ๐ง๐๐ ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ + ๐ฏ๐ด๐ฐ ๐๐ฅ๐๐๐ง ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ ๐๐ฅ๐ ๐ญ๐ฌ๐ฌ% ๐๐ฃ๐จ-๐ฅ๐๐ฆ๐๐๐๐ก๐ง ๐๐ก ๐ ๐ฌ ๐ง๐๐ฆ๐ง๐๐ ๐ฅ๐๐ซ๐๐ฏ ๐๐ข๐ก๐๐๐๐จ๐ฅ๐๐ง๐๐ข๐ก!
ZERO streamed experts.
๐ข๐ก๐. ๐ญ๐ฎ๐ด๐๐. ๐๐๐ซ. ๐ฆ๐ฃ๐๐ฅ๐. ๐
@mr_r0b0t and I are continuing to refine REXL3 before its release. More on that soon! ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ง๐๐๐ฆ ๐๐ฆ ๐ช๐๐ฌ ๐ ๐๐จ๐๐๐ ๐๐ข๐ฅ ๐๐ข๐๐๐ ๐๐.
Just YESTERDAY, I shared my goal of bringing extremely aggressive, high-quality quantization to people who don't have access to massive compute clusters.
With the support of @AWERXAI, I've been working tirelessly to push that vision forward.
And now we're seeing a 1.62 bpw expert quant outperform higher-bitrate alternatives on actual tasks, not just token-level fidelity measurements.
This doesn't establish mathematical losslessness or superiority on every possible workload. These are matched subsets of nine benchmark suites, not full public leaderboard scores.
But it demonstrates something IMPORTANT:
๐ ๐ข๐ฅ๐ ๐๐๐ง๐ฆ ๐๐ข๐ก'๐ง ๐๐จ๐ง๐ข๐ ๐๐ง๐๐๐๐๐๐ฌ ๐ ๐๐๐ก ๐๐๐ง๐ง๐๐ฅ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ.
And more hardware doesn't automatically mean you need it!
Huge respect to @jayleaton for his contributions and for giving the community more ways to run these incredible models.
And thank you @AWERXAI for supporting this work. ๐
๐ ๐ ๐ฌ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ ๐ค๐จ๐๐ก๐ง
huggingface.co/vcruz305/DSV4โฆ
๐ ๏ธ ๐ข๐ก๐-๐ฆ๐ฃ๐๐ฅ๐ ๐๐๐๐ ๐ฅ๐๐๐๐ฃ๐
github.com/vcruz305/DSV4.1-Fโฆ
๐๐ฅ๐ข๐ก๐ง๐๐๐ฅ ๐ ๐ข๐๐๐๐ฆ. ๐๐ข๐๐๐ ๐๐๐ฅ๐๐ช๐๐ฅ๐. ๐ฅ๐๐๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ.
๐๐๐ง'๐ฆ ๐๐๐๐ฃ ๐ฃ๐จ๐ฆ๐๐๐ก๐! ๐๐ฅ
๐จ ๐ ๐๐จ๐ฆ๐ง ๐๐๐๐๐๐ฉ๐๐ ๐ฆ๐ข๐ ๐๐ง๐๐๐ก๐ ๐๐ก๐๐ฅ๐๐๐๐๐๐ ๐ข๐ก ๐ข๐ก๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐! ๐งช๐ฅ
With the support of @AWERXAI, I'm excited to release something VERY special for the local AI community!
๐ง @deepseek_ai ๐๐ฒ๐ฒ๐ฝ๐ฆ๐ฒ๐ฒ๐ธ ๐ฉ๐ฐ.๐ญ ๐๐น๐ฎ๐๐ต ๐ญ๐ฌ๐ญ๐ณ
๐ฆ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ ๐ฎ๐ ๐ท๐๐๐ ๐ญ.๐ฒ๐ฎ ๐ฏ๐ฝ๐ ๐ฒ๐
๐ฝ๐ฒ๐ฟ๐๐
๐ป ๐ต๐ต.๐ฒ๐ญ% ๐๐ข๐๐ ๐ฎ๐ป๐๐๐ฒ๐ฟ-๐๐ผ๐ธ๐ฒ๐ป ๐ฎ๐ด๐ฟ๐ฒ๐ฒ๐บ๐ฒ๐ป๐!
โก ๐ฏ๐ฑ.๐ฑ ๐๐ผ๐ธ/๐ ๐ฑ๐ฒ๐ฐ๐ผ๐ฑ๐ฒ ๐ผ๐ป ๐๐๐๐ !
๐ ๐ญ,๐ญ๐ด๐ต ๐๐ผ๐ธ/๐ ๐ ๐๐ซ ๐ฃ๐ฅ๐๐๐๐๐!
๐ง ๐ฎ๐ฎ๐ต๐ ๐๐ง๐ซ (๐๐๐ถ๐น๐น ๐๐ผ๐ฟ๐ธ๐ถ๐ป๐ด ๐๐ผ ๐ฝ๐๐๐ต ๐ถ๐ ๐ณ๐๐ฟ๐๐ต๐ฒ๐ฟ!)
๐๐๐ ๐ข๐ก ๐ข๐ก๐. ๐๐๐ซ. ๐ฆ๐ฃ๐๐ฅ๐. ๐คฏ
And YES, the quantized weights are AVAILABLE NOW! ๐
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ง๐๐ ๐๐๐ฆ๐ง ๐ณ๐ฎ ๐๐ข๐จ๐ฅ๐ฆ ๐๐๐ฉ๐ ๐๐๐๐ก ๐๐ก๐ฆ๐๐ก๐!
Just a few days ago, I published my article about @nvidiaai's FP4-Local format: The Good, The Bad & The Ugly.
One thing really stuck with me...
NVIDIA demonstrated what was possible when aggressive quantization and intelligent optimization come together.
But there's a problem.
๐ฅ๐๐ฃ๐ฅ๐ข๐๐จ๐๐๐ก๐ ๐ ๐๐ฆ๐ฆ๐๐ฉ๐ ๐ค๐จ๐๐ก๐ง๐๐ญ๐๐ง๐๐ข๐ก ๐ง๐ฅ๐๐๐ก๐๐ก๐ ๐ฃ๐๐ฃ๐๐๐๐ก๐๐ฆ ๐๐ฆ ๐ข๐จ๐ง ๐ข๐ ๐ฅ๐๐๐๐ ๐๐ข๐ฅ ๐ ๐ข๐ฆ๐ง ๐๐ข๐๐๐ ๐๐ ๐๐ก๐ง๐๐จ๐ฆ๐๐๐ฆ๐ง๐ฆ.
That inspired me.
I've been developing my own SAGE-EXL3 process, and I wanted to see just how far I could push the latest DeepSeek Flash release while keeping the results accessible to the community.
So I spent the last 72 hours pushing the limits.
And the results genuinely surprised me! ๐ฅ
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ง๐๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ ๐๐ฅ๐ ๐๐ฅ๐๐ญ๐ฌ!
I measured my 1.62 bpw expert quant against DeepSeek's native FP4 release checkpoint using held-out sequences and full-vocabulary token predictions.
And when I saw the CODE results, I could barely believe it!
๐งช ๐๐๐๐๐๐๐ง๐ฌ ๐ฉ๐ฆ ๐๐๐๐ฃ๐ฆ๐๐๐'๐ฆ ๐ก๐๐ง๐๐ฉ๐ ๐๐ฃ๐ด/๐๐ฃ๐ฐ ๐ฅ๐๐๐๐๐ฆ๐
๐ป ๐๐ข๐๐ โ ๐๐๐บ๐ฎ๐ป๐๐๐ฎ๐น
โ
99.08% Top-1 Agreement
โ
๐ต๐ต.๐ฒ๐ญ% ๐๐ก๐ฆ๐ช๐๐ฅ-๐ข๐ก๐๐ฌ ๐๐๐ฅ๐๐๐ ๐๐ก๐ง!
โ
KL Divergence: 0.0186
๐ง ๐ฅ๐๐๐ฆ๐ข๐ก๐๐ก๐ โ ๐ ๐๐ง๐-๐ฑ๐ฌ๐ฌ
โ
96.04% Top-1 Agreement
โ
97.98% Answer-Only Agreement
โ
KL Divergence: 0.0349
๐ข ๐ ๐๐ง๐ โ ๐๐ฆ๐ ๐ด๐
โ
95.56% Top-1 Agreement
โ
94.19% Answer-Only Agreement
โ
KL Divergence: 0.0477
๐ ๐ข๐ฉ๐๐ฅ๐๐๐ ๐๐๐๐-๐ข๐จ๐ง ๐๐๐๐๐๐๐ง๐ฌ
๐ 94.52% Top-1 Agreement
๐ Mean KL: 0.0982
๐ฏ Median KL: 0.00019
๐ก๐๐๐ฅ-๐๐ข๐ฆ๐ฆ๐๐๐ฆ๐ฆ ๐๐ข๐๐ ๐ง๐ข๐๐๐ก ๐๐๐๐๐๐๐ง๐ฌ ๐๐ง ๐๐จ๐ฆ๐ง ๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ! ๐คฏ
These are direct teacher-forced fidelity measurements against native FP8, not task-level pass rates.
But seeing this level of agreement at such aggressive compression is EXACTLY what I was working toward!
โโโโโโโโโโโโโโโโโโโโ
โก ๐๐ก๐ ๐ฌ๐๐ฆ, ๐๐ง ๐๐๐ง๐จ๐๐๐๐ฌ ๐ฅ๐จ๐ก๐ฆ ๐ข๐ก ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐!
Not two Sparks.
Not four Sparks.
Not an expensive rented GPU cluster.
๐ข๐ก๐ ๐ญ๐ฎ๐ด๐๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐.
My latest vLLM measurements:
โก Decode: 35.5 tok/s
๐ Maximum measured prefill: 1,189 tok/s
For a model this large, compressed this aggressively, and maintaining this level of fidelity...
๐ง๐๐๐ง'๐ฆ ๐ ๐๐๐ ๐๐๐๐ ๐๐ข๐ฅ ๐๐ข๐๐๐ ๐๐! ๐
And remember, 1.62 bpw refers to the routed experts, not every parameter in the full model.
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ช๐๐ฌ ๐ง๐๐๐ฆ ๐ ๐๐ง๐ง๐๐ฅ๐ฆ.
I have a simple goal.
๐ ๐๐๐ ๐ฃ๐ข๐ช๐๐ฅ๐๐จ๐ ๐๐ ๐๐๐๐๐ฆ๐ฆ๐๐๐๐ ๐ง๐ข ๐ฃ๐๐ข๐ฃ๐๐ ๐ช๐๐ข ๐๐ข๐ก'๐ง ๐๐๐ฉ๐ ๐๐๐๐๐ฆ๐ฆ ๐ง๐ข ๐๐๐ง๐๐๐๐ก๐ง๐๐ฅ๐ฆ.
I don't want the future of local AI to be determined by who can rent the most GPUs or afford the largest training runs.
I want developers, independent researchers and enthusiasts to have the freedom to experiment, quantize, optimize and run powerful models on hardware they actually OWN.
NVIDIA's FP4-Local research showed me just how much potential remains in aggressive quantization.
My goal with SAGE-EXL3 is to keep pushing that frontier while making advanced quantization more practical for the wider community.
Today, I'm sharing the quantized checkpoint and the one-Spark serving recipe.
๐ง๐๐๐ฆ ๐๐ฆ ๐๐จ๐ฆ๐ง ๐ง๐๐ ๐๐๐๐๐ก๐ก๐๐ก๐.
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ก๐ข๐ช ๐๐ข๐ฅ ๐ง๐๐ ๐ฅ๐๐๐ ๐ง๐๐ฆ๐ง!
The token-level fidelity results are incredible, but I'm not stopping there.
I'm currently running a broader evaluation campaign to measure how closely this quant preserves the native FP8 model's actual task performance.
๐ป HumanEval+ / MBPP+
๐ง MMLU-Pro STEM / MATH-500
๐ฌ SciCode / LiveCodeBench
๐ง BFCL / Multi-step tool chains
๐ MGSM
๐ง๐๐ ๐๐ข๐๐ ๐๐ฆ ๐ง๐ข ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ง๐๐๐ง ๐๐๐๐ฅ๐๐ฆ๐ฆ๐๐ฉ๐ ๐๐ข๐ ๐ฃ๐ฅ๐๐ฆ๐ฆ๐๐ข๐ก ๐๐ข๐๐ฆ๐ก'๐ง ๐๐๐ฉ๐ ๐ง๐ข ๐ ๐๐๐ก ๐๐๐๐ฅ๐๐ฆ๐ฆ๐๐ฉ๐ ๐ค๐จ๐๐๐๐ง๐ฌ ๐๐ข๐ฆ๐ฆ!
Those task-level results are coming next! ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐๐ก๐ ๐ข๐ก๐ ๐๐๐ง๐ง๐๐ ๐ง๐๐๐ฆ๐๐ฅ...
@mr_r0b0t and I have also been working on an GB10 specialized inference engine called ๐ฅ๐๐ซ๐๐ฏ.
Early testing has been VERY exciting, including 60 tok/s with bursts reaching 74tok/s!
We're putting the finishing touches on it and making sure everything is solid before releasing it.
More on that VERY soon. ๐
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ ๐๐จ๐๐ ๐ง๐๐๐ก๐ ๐ฌ๐ข๐จ!
To @AWERXAI for supporting my work and helping make this contribution to the community possible.
To @nvidiaai for the FP4-Local research that inspired me to push this experiment even further.
To @justinn_builds for his initial vllm TP4 recipe that got me started in the right direction for loading this model up.
To @mr_r0b0t for collaborating with me on what's coming next!
And to @deepseek_ai for continuing to release powerful open-weight models that make community experiments like this possible.
๐ง๐๐ ๐๐๐ฆ๐ง ๐ฃ๐๐ฅ๐ง ๐ข๐ ๐ข๐ฃ๐๐ก ๐๐ ๐๐ฆ ๐ช๐๐๐ง ๐ง๐๐ ๐๐ข๐ ๐ ๐จ๐ก๐๐ง๐ฌ ๐๐๐ก ๐๐จ๐๐๐ ๐ข๐ก ๐ง๐ข๐ฃ ๐ข๐ ๐๐ง. ๐
๐ ๐๐ข๐ช๐ก๐๐ข๐๐ ๐ ๐ฌ ๐ฆ๐๐๐-๐๐ซ๐๐ฏ
huggingface.co/vcruz305/DSV4โฆ
๐ ๏ธ ๐ข๐ก๐-๐ฆ๐ฃ๐๐ฅ๐ ๐ฅ๐๐๐๐ฃ๐
github.com/vcruz305/DSV4.1-Fโฆ
๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐.
๐ญ.๐ฒ๐ฎ ๐๐ฃ๐ช ๐๐ซ๐ฃ๐๐ฅ๐ง๐ฆ.
๐ต๐ต.๐ฒ๐ญ% ๐๐ข๐๐ ๐๐ก๐ฆ๐ช๐๐ฅ ๐๐๐ฅ๐๐๐ ๐๐ก๐ง.
๐๐๐ง'๐ฆ ๐๐๐๐ฃ ๐ฃ๐จ๐ฆ๐๐๐ก๐ ๐๐ข๐๐๐ ๐๐ ๐๐ข๐ฅ๐ช๐๐ฅ๐! ๐๐ฅ
๐จ ๐ฆ๐ฃ๐๐๐ ๐๐จ๐ก๐ก๐ฌ ๐ช๐๐ฆ ๐ ๐๐ก๐๐ ๐๐ซ?! ๐ฐ๐ฅ
I KNEW there was something special about this model! ๐คฏ
I used Space Bunny for FREE through @NousResearchโs Portal and @OpenRouter at work, and let me tell youโฆ
๐ง๐๐๐ฆ ๐ ๐ข๐๐๐ ๐๐ฆ ๐๐ก๐๐ฅ๐๐๐๐๐๐!
โก BLAZING FAST
๐ง Excellent at understanding complex tasks
๐ป Fantastic for coding and agentic workflows
But the BEST part?
๐ ๐๐๐๐กโ๐ง ๐๐๐ฉ๐ ๐ง๐ข ๐๐ซ๐ฃ๐๐๐๐ก ๐ ๐จ๐๐. ๐๐ง ๐๐จ๐ฆ๐ง ๐ช๐ข๐ฅ๐๐๐! ๐ฅ
And now @MiniMax_AI confirms Space Bunny was an early version of M3.1 Flash!
๐ฐ 200 TRILLION+ tokens processed anonymously!
๐ New release: 170+ tok/s median!
๐ฐ 70% lower agentic task costs than its predecessor!
THIS is the kind of practical, efficient AI Iโm excited about!
Huge congratulations to the MiniMax team! ๐๐
Now get me those weightssssss ๐
MiniMax M3.1 Flash: Space Performance + Bunny Speed
๐๐ฐ Yes, Space Bunny - which has topped global leaderboards with 200T+ tokens - was an earlier version of M3.1 Flash.
๐ฐRedefining the performance economics of agentic AI. M3.1 Flash achieves frontier-level intelligence across key tasks such as Cowork (Automation-Bench: 62%; ALE: 30%), Coding (DeepSWE: 74%) and Visual Reasoning (BabyVision: 91%), at 1/3 the cost of M3 and 3x the speed.
API pricing (flat rate): $0.15 / $0.60 per 1M input/output tokens, with cache reads at $0.015 / 1M tokens.
Model weights will arrive on Oct 23.
API: platform.minimax.io
M Plan: minimax.io/m-plan
MiniMax Code for desktop: agent.minimax.io/download
Correction, @NVIDIAAI spoken about this! You just need to send them an email asking if this is supported or not and youll get something like what my friend @MarkusEicher70 got back from them:
"NVIDIA DOES NOT officially support or recommend manually overriding the GPU clock limits on DGX Spark systems using commands such as: sudo nvidia-smi -lgc"
Unless youre seeing extreme performance degredation on your DGX Spark due to high heats and youre also up to date on all updates especially kernel and firmware, then theres zero reason to underclock.
There's a big argument on whether you _should_ cap the clock rates on your DGX Sparks because they are, in theory, supposed to cool themselves to safe levels.
NVIDIA doesn't recommend capping them, but they also don't recommend not capping them. Here's my thoughts on this:
I have a couple of DGX Sparks that are marginal when running heavy prefill on GLM 5.3. This model pushes the box to the max. I'm not kidding - it jumps from ~47C to 87C in under a minute. During a heavy TP=3 prefill test, one box reliably powers itself off (!) without a clock cap. With a clock cap, it stays on.
I have an additional fan moving air over the Sparks. I can add additional cooling, but this is a datapoint where NVIDIA's guidance is, in fact, wrong. Not all DGX Sparks can ramp their fans and/or throttle their own power fast enough to prevent thermal shutdown without a clock cap.
2200 MHz is enough to keep it alive. You know what? I'm happy to give up a small 1-2% gap in peak performance to keep the Sparks alive. Heat over time is one of the silent killer of chips.
๐จ @nvidiaai FP4-LOCAL: THE GOOD, THE BAD & THE UGLY! ๐ฅ
I tested Qwen3.8-Flash-Next 4 ways. FP4-Local TP1 & 2, NVFP4 and EXL3
FP4: 1 Spark: 90.8% SixCat, 68 tok/s. 2 Sparks: 32% slower decode. DIY quantization? That's the ugly part.
My full article ๐
๐จ @nvidiaai ๐๐จ๐ฆ๐ง ๐ฃ๐จ๐ฆ๐๐๐ ๐ง๐๐ ๐ข๐ก๐-๐ฆ๐ฃ๐๐ฅ๐ ๐๐ฅ๐ข๐ก๐ง๐๐๐ฅ ๐๐ข๐ฅ๐ช๐๐ฅ๐! ๐บ๐ธ๐ฅ
๐ง ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐:
1 MILLION native context tokens + 84.17% SixCat!
โก ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐๐ข๐๐ง + ๐๐ถ๐๐ถ๐๐ผ๐ฟ๐ฟ ๐๐๐น๐ฎ๐๐ต:
87.8 tok/s single-stream decode + 195.1 tok/s balanced throughput!
๐ฅ๏ธ ๐ง๐ช๐ข ๐ ๐ข๐๐๐๐ฆ. ๐ง๐ช๐ข ๐๐๐๐๐๐ฅ๐๐ก๐ง ๐ฆ๐ง๐ฅ๐๐ก๐๐ง๐๐ฆ. ๐ข๐ก๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐!
And YES, these are my actual measurements from the DGX Spark sitting in my home! ๐คฏ
After NVIDIA gave me pre-release access to Nemotron 3.5 Super VL, I've spent the past week benchmarking, optimizing, and experimenting with these new models.
But I wanted to answer something more important than which model has the highest intelligence score...
๐ช๐๐๐๐ ๐ ๐ข๐๐๐ ๐๐๐ง๐จ๐๐๐๐ฌ ๐๐๐ง๐ฆ ๐ช๐ข๐ฅ๐ ๐๐ข๐ก๐ ๐๐๐ฆ๐ง๐๐ฅ, ๐๐ก๐ ๐ช๐๐๐๐ ๐ข๐ก๐ ๐๐๐ก ๐๐๐ก๐๐๐ ๐ ๐ข๐ฅ๐ ๐ช๐ข๐ฅ๐?
I tested both models separately on the SAME GB10 DGX Spark.
Not two Sparks.
Not a datacenter cluster.
๐ข๐ก๐. ๐๐๐ซ. ๐ฆ๐ฃ๐๐ฅ๐.
And these results are INCREDIBLY interesting for the future of local AI!
โโโโโโโโโโโโโโโโโโโโ
๐ง ๐ฃ๐๐ฅ๐ง ๐ญ: ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐ โ ๐ง๐๐ ๐ญ๐ ๐๐ข๐ก๐ง๐๐ซ๐ง ๐ฃ๐ข๐ช๐๐ฅ๐๐ข๐จ๐ฆ๐!
120B total parameters.
12B active parameters.
Multimodal reasoning, coding, tools, image, document and video understanding.
And here's what REALLY caught my attention...
๐ ๐๐จ๐๐ ๐ญ,๐ฌ๐ฐ๐ด,๐ฑ๐ณ๐ฒ ๐ก๐๐ง๐๐ฉ๐ ๐๐ข๐ก๐ง๐๐ซ๐ง ๐ช๐๐ก๐๐ข๐ช ๐ข๐ก ๐ข๐ก๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐! ๐คฏ
And YES, I've personally tested the FULL 1M-token context window on my single Spark and confirmed it WORKS! ๐ฅ
For comparison, Qwen3.8-Flash-Next has a native context window of 262,144 tokens.
Qwen recommends using RoPE scaling techniques such as YaRN to extend beyond its native context.
๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐ ๐ฆ๐จ๐ฃ๐ฃ๐ข๐ฅ๐ง๐ฆ ๐ฐร ๐ง๐๐๐ง ๐ก๐๐ง๐๐ฉ๐ ๐๐ข๐ก๐ง๐๐ซ๐ง ๐ช๐๐ง๐๐ข๐จ๐ง ๐ฌ๐ฎ๐ฅ๐ก!
And let me emphasize...
๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐! ๐ก๐ข๐ง ๐ง๐ช๐ข!
Why am I so excited about this?
Because for everyday and enterprise AI workloads, a massive context window can be MORE useful than simply having a slightly higher intelligence score.
Think about the possibilities:
โ
Entire codebases and large repositories
โ
Massive infrastructure logs and incident histories
โ
Enterprise documentation and policies
โ
Long-running autonomous agents
โ
Multimodal document analysis
โ
Extended research and investigation workflows
โ
Larger working histories without constant summarization
Instead of repeatedly compressing information to fit inside a smaller context window, you have significantly more room to work!
Now, 4ร the context capacity doesn't mean 4ร the reasoning quality or processing speed.
But having a FULL native 1M-token window working on a single Spark that I own at home is a HUGE DEAL!
๐ง๐๐๐ฆ ๐๐ฆ ๐ง๐๐ ๐๐๐ก๐ ๐ข๐ ๐๐ข๐๐๐ ๐๐ ๐ฃ๐ฅ๐ข๐๐ฅ๐๐ฆ๐ฆ ๐ ๐ช๐๐ก๐ง ๐ง๐ข ๐ฆ๐๐! ๐ฅ
โโโโโโโโโโโโโโโโโโโโ
โก ๐ฃ๐๐ฅ๐ง ๐ฎ: ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐๐ข๐๐ง โ ๐ง๐๐ ๐๐ข๐๐๐ ๐ฆ๐ฃ๐๐๐ ๐ ๐๐ฆ๐ง๐๐ฅ!
Now let's talk about Bolt, because NVIDIA has been COOKING with this one too! ๐
74B total parameters.
Only 9B active.
An official 24GB-class IQ2 checkpoint.
262,144-token context support.
Designed to bring fast, capable agentic AI to smaller local hardware footprints.
But NVIDIA didn't stop at the model itself...
They also released ๐๐ถ๐๐ถ๐๐ผ๐ฟ๐ฟ, a speculative drafting model used with their ๐๐๐น๐ฎ๐๐ต speculative decoding system.
Naturally, I HAD to test it on my Spark!
I ran the same Bolt IQ2 target through SixCat Speed with and without the LiLiCorr DFlash drafter.
Same GB10 hardware.
Same target checkpoint.
Same vLLM engine.
Same benchmark workloads.
And the results were WILD! ๐คฏ
๐ฅ ๐๐ข๐๐ง ๐ฆ๐ฃ๐๐๐: ๐ก๐ข ๐๐ฅ๐๐๐ง ๐๐ ๐๐๐๐๐๐ข๐ฅ๐ฅ ๐๐๐๐๐ฆ๐
โก ๐ฆ๐๐ก๐๐๐-๐ฆ๐ง๐ฅ๐๐๐ ๐๐๐๐ข๐๐:
30.9 โ 87.8 TOK/S
๐ ๐ฎ.๐ด๐ฐร ๐๐๐ฆ๐ง๐๐ฅ!
๐ฅ ๐๐๐๐๐ก๐๐๐ ๐ง๐๐ฅ๐ข๐จ๐๐๐ฃ๐จ๐ง (๐ด ๐๐ข๐ก๐๐จ๐ฅ๐ฅ๐๐ก๐ง ๐ฅ๐๐ค๐จ๐๐ฆ๐ง๐ฆ):
136.5 โ 195.1 OUTPUT TOK/S
๐ +๐ฐ๐ฏ% ๐๐๐๐๐๐ฅ ๐ง๐๐ฅ๐ข๐จ๐๐๐ฃ๐จ๐ง!
๐ฅ ๐ฆ๐๐ก๐๐๐-๐ฆ๐ง๐ฅ๐๐๐ ๐ฃ๐ฅ๐๐๐๐๐:
1,584 โ 1,328 tok/s (โ16%)
โฑ๏ธ ๐๐๐๐๐ก๐๐๐ ๐ง๐๐ ๐ ๐ง๐ข ๐๐๐ฅ๐ฆ๐ง ๐ง๐ข๐๐๐ก:
1.68 โ 1.87 seconds (+0.19 seconds)
And here's the best part...
โ
All THREE DFlash speed profiles completed 32/32 requests each!
โ
Approximately 55.5% of drafted tokens were accepted!
โ
vLLM speculative decoding counters confirmed LiLiCorr was actively being used!
โ
No memory guard stops or swap growth observed!
๐๐๐ ๐ข๐ฆ๐ง ๐ฏร ๐ง๐๐ ๐ฆ๐๐ก๐๐๐-๐ฆ๐ง๐ฅ๐๐๐ ๐๐๐๐ข๐๐ ๐ฆ๐ฃ๐๐๐ ๐จ๐ฆ๐๐ก๐ ๐ง๐๐ ๐ฆ๐๐ ๐ ๐๐ข๐๐ง ๐ง๐๐ฅ๐๐๐ง ๐ข๐ก ๐ง๐๐ ๐ฆ๐๐ ๐ ๐ฆ๐ฃ๐๐ฅ๐!
There are some prefill and latency trade-offs, but the decoding improvement is absolutely impressive.
And remember, this is a model with a target checkpoint of approximately 24GB!
The 24GB figure is the target-model directory size, not the complete memory footprint with LiLiCorr loaded.
โโโโโโโโโโโโโโโโโโโโ
๐งช ๐ฃ๐๐ฅ๐ง ๐ฏ: ๐ ๐ฌ ๐ฆ๐๐ซ๐๐๐ง ๐ค๐จ๐๐๐๐ง๐ฌ ๐๐๐ก๐๐๐ ๐๐ฅ๐๐ฆ!
Speed is great, but what about INTELLIGENCE?
Both models completed my SixCat evaluation suite:
120 questions.
6 categories.
Strict scoring.
Thinking enabled.
Code executed and graded.
๐ข ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐ (๐ญ๐ฎ๐ฌ๐-๐๐ญ๐ฎ๐)
๐ ๐ด๐ฐ.๐ญ๐ณ% โ ๐ญ๐ฌ๐ญ/๐ญ๐ฎ๐ฌ ๐ฃ๐๐ฆ๐ฆ๐๐!
๐ฃ ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐๐ข๐๐ง (๐ณ๐ฐ๐-๐๐ต๐)
๐ ๐ณ๐ณ.๐ฑ๐ฌ% โ ๐ต๐ฏ/๐ญ๐ฎ๐ฌ ๐ฃ๐๐ฆ๐ฆ๐๐!
๐ ๐ค๐จ๐๐๐๐ง๐ฌ ๐๐ฅ๐๐๐๐๐ข๐ช๐ก: ๐๐ข๐๐ง โ ๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐
๐ง Knowledge: 60% โ 85%
๐ข Math: 100% โ 100%
๐ฏ Truthfulness: 80% โ 85%
๐ Instruction Following: 50% โ 50%
๐ป Code: 85% โ 100%
๐ง Tools: 90% โ 85%
๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐ ๐ช๐๐ก๐ฆ ๐ข๐ฉ๐๐ฅ๐๐๐ ๐๐ฌ ๐ฒ.๐ฒ๐ณ ๐ฃ๐๐ฅ๐๐๐ก๐ง๐๐๐ ๐ฃ๐ข๐๐ก๐ง๐ฆ!
But don't underestimate Bolt!
โ
100% in Math!
โ
90% in Tool Use!
โ
77.5% overall with a much smaller model footprint!
These scores are from the earlier SixCat quality runs. The LiLiCorr experiment is a new SPEED benchmark, not a new quality evaluation.
Both quality receipts also flagged instruction truncation or looping, so the results should be interpreted with those limitations.
โโโโโโโโโโโโโโโโโโโโ
๐๏ธ ๐ฃ๐๐ฅ๐ง ๐ฐ: ๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐ ๐๐ ๐๐ข๐๐ง + ๐๐๐๐๐ฆ๐ โ ๐ง๐๐ ๐ฅ๐๐๐ ๐ง๐ฅ๐๐๐-๐ข๐๐!
Now that we have both quality and speed measurements, here's how my tested configurations compare.
๐ข ๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐ โ ๐ง๐๐ ๐๐๐๐-๐๐๐ฃ๐๐๐๐๐๐ง๐ฌ ๐๐๐๐ ๐ ๐ข๐๐๐
๐ SixCat: 84.17%
๐ง Native context: 1,048,576 tokens
๐ฆ Model directory: 75.06 GB
โก Single-stream decode: 37.3 tok/s
๐ Balanced throughput C=8: 90.9 tok/s
โฑ๏ธ Long-prompt TTFT p50, C=8: 4.47 seconds
Inference: NVIDIA NVFP4, vLLM 0.31.0, FlashInfer, MTP-5.
๐ฃ ๐๐ข๐๐ง + ๐๐๐๐๐๐ข๐ฅ๐ฅ ๐๐๐๐๐ฆ๐ โ ๐ง๐๐ ๐๐๐ฆ๐ง ๐ช๐ข๐ฅ๐๐๐ฅ
๐ SixCat: 77.50% (earlier no-draft quality run)
๐ง Native context: 262,144 tokens
๐ฆ Bolt target directory: 24.12 GB
โก Single-stream decode: 87.8 tok/s
๐ Balanced throughput C=8: 195.1 tok/s
โฑ๏ธ Balanced TTFT p50: 1.87 seconds
Inference: Mixed ModelOpt IQ2, vLLM 0.32.0rc1 development build, B12X 1.5.1, FlashInfer, LiLiCorr DFlash.
๐๐ข๐๐ง + ๐๐๐๐๐ฆ๐ ๐๐๐๐๐ฉ๐๐ฅ๐ฆ:
๐ฅ ๐ฎ.๐ฏ๐ฑร ๐๐๐ฆ๐ง๐๐ฅ than Super VL on measured single-stream decode!
๐ฅ ๐ฎ.๐ญ๐ฑร ๐๐๐๐๐๐ฅ balanced output throughput at 8 concurrent requests!
But Super VL brings:
๐ง Higher overall SixCat score.
๐ 4ร the native context capacity.
๐๏ธ Powerful multimodal reasoning.
๐ฏ A compelling foundation for complex agent orchestration.
These are measured deployment configurations with different inference engines, quantizations and speculative decoding strategies. This isn't an isolated architecture comparison.
๐๐ก๐ ๐ง๐๐๐ง'๐ฆ ๐๐ซ๐๐๐ง๐๐ฌ ๐ช๐๐๐ง ๐ ๐๐๐๐ฆ ๐ง๐๐๐ฆ๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ ๐๐ก๐ง๐๐ฅ๐๐ฆ๐ง๐๐ก๐!
I care about what I can actually run and accomplish with these models on my own hardware!
โโโโโโโโโโโโโโโโโโโโ
๐บ๐ธ ๐ฃ๐๐ฅ๐ง ๐ฑ: ๐๐ ๐๐ฅ๐๐๐๐ก ๐๐ ๐๐ฆ ๐ฃ๐จ๐ฆ๐๐๐ก๐ ๐ง๐๐ ๐ข๐ก๐-๐ฆ๐ฃ๐๐ฅ๐ ๐๐ฅ๐ข๐ก๐ง๐๐๐ฅ!
One of the things I LOVE most about this release is seeing an American company like NVIDIA pushing open-weight local AI forward at this level!
NVIDIA's published EXO Labs/local.ai results place Nemotron 3.5 Super VL on the intelligence-versus-task-completion-time Pareto frontier for a SINGLE 128GB DGX Spark.
That's a published frontier evaluation, separate from my SixCat results.
And then we have Bolt, with LiLiCorr DFlash delivering nearly 88 tokens per second in my single-stream test and over 195 output tokens per second on the balanced concurrent workload!
Not on a rack of GPUs.
๐ข๐ก ๐ง๐๐ ๐ฆ๐ฃ๐๐ฅ๐ ๐ฆ๐๐ง๐ง๐๐ก๐ ๐๐ก ๐ ๐ฌ ๐๐ข๐ ๐!
This is what real progress looks like to me.
Not simply releasing the BIGGEST model possible.
But delivering:
โ
More useful intelligence per GB
โ
Faster task execution
โ
More concurrent work
โ
Larger native context windows
โ
Better deployment efficiency
โ
Open weights people can actually experiment with!
๐ง๐๐ ๐๐ข๐๐ ๐๐ฆ๐ก'๐ง ๐๐จ๐ฆ๐ง ๐ ๐๐ซ๐๐ ๐จ๐ ๐๐ก๐ง๐๐๐๐๐๐๐ก๐๐.
๐๐ง'๐ฆ ๐ ๐๐ซ๐๐ ๐จ๐ ๐จ๐ฆ๐๐๐จ๐๐ก๐๐ฆ๐ฆ! ๐ฅ
โโโโโโโโโโโโโโโโโโโโ
โก ๐ฃ๐๐ฅ๐ง ๐ฒ: ๐ง๐ช๐ข ๐ ๐ข๐๐๐๐ฆ. ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐.
Now you can probably see exactly where I'm going with all of this... ๐
What if we combine the strengths of BOTH models?
๐ง ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐ โ ๐ ๐๐ฆ๐ง๐๐ฅ ๐๐๐๐ก๐ง
Handling large-context reasoning, multimodal understanding, complex decisions and orchestration.
โก ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐๐ข๐๐ง โ ๐ฆ๐จ๐-๐๐๐๐ก๐ง
Handling fast delegated work, coding, tool execution and high-throughput tasks.
The goal?
๐ง๐ช๐ข ๐ฃ๐ข๐ช๐๐ฅ๐๐จ๐ ๐ ๐ข๐๐๐๐ฆ. ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐. ๐๐จ๐๐๐ฌ ๐๐ข๐๐๐.
Imagine the lead model working with a massive context window, coordinating specialized workers that can execute tasks quickly without every request needing the larger model!
That is the kind of practical agentic system I want to build.
Today's model-to-model speed and quality comparisons come from separate deployments. Simultaneous residency, shared resource limits and actual master-worker delegation are the next things to validate.
And YES, I've already been experimenting with smaller EXL3 models to make this vision more practical! ๐
โโโโโโโโโโโโโโโโโโโโ
๐ฌ ๐ ๐ค๐จ๐๐๐ ๐ก๐ข๐ง๐ ๐ข๐ก ๐ง๐๐ฆ๐ง๐๐ก๐
All tests were performed on my single home GB10 DGX Spark.
I successfully tested Super VL's full native 1M-token context window on this hardware.
Bolt's new LiLiCorr numbers are speed-only measurements using the same Bolt target and vLLM engine as the matching no-draft baseline.
The speed results shown above are from the reported SixCat Speed workloads. Disk measurements are not peak runtime memory usage.
My purpose is to share reproducible, real-world results rather than suggest either configuration represents its maximum possible performance.
โโโโโโโโโโโโโโโโโโโโ
๐ ๐ ๐๐จ๐๐ ๐ง๐๐๐ก๐ ๐ฌ๐ข๐จ ๐ง๐ข @nvidiaai!
Being given pre-release access to Nemotron 3.5 Super VL was an incredible opportunity, and I've genuinely enjoyed spending the past week pushing these models through their paces.
NVIDIA isn't just releasing impressive models. They're helping make powerful AI more accessible to developers, researchers and enthusiasts who want to run these systems on hardware they can own.
And that's something I'm incredibly passionate about.
๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐. ๐ ๐ข๐ฅ๐ ๐๐ก๐ง๐๐๐๐๐๐๐ก๐๐. ๐ ๐ข๐ฅ๐ ๐ฆ๐ฃ๐๐๐. ๐ ๐ข๐ฅ๐ ๐ฃ๐ข๐ฆ๐ฆ๐๐๐๐๐๐ง๐๐๐ฆ. ๐
๐ ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐ฆ๐จ๐ฃ๐๐ฅ ๐ฉ๐ ๐ก๐ฉ๐๐ฃ๐ฐ
huggingface.co/nvidia/NVIDIAโฆ
๐ ๐ก๐๐ ๐ข๐ง๐ฅ๐ข๐ก ๐ฏ.๐ฑ ๐๐ข๐๐ง ๐ฎ๐ฐ๐๐
huggingface.co/nvidia/NVIDIAโฆ
๐ ๐ก๐ฉ๐๐๐๐ ๐๐๐๐๐๐ข๐ฅ๐ฅ ๐๐๐๐๐ฆ๐ ๐๐ฅ๐๐๐ง๐๐ฅ
huggingface.co/nvidia/NVIDIAโฆ
๐ ๐ก๐ฉ๐๐๐๐ ๐ง๐๐๐๐ก๐๐๐๐ ๐๐๐ข๐
developer.nvidia.com/blog/nvโฆ
๐ง๐ช๐ข ๐ ๐ข๐๐๐๐ฆ. ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐. ๐ง๐๐ ๐๐ซ๐ฃ๐๐ฅ๐๐ ๐๐ก๐ง๐ฆ ๐๐ฅ๐ ๐๐จ๐ฆ๐ง ๐๐๐ง๐ง๐๐ก๐ ๐ฆ๐ง๐๐ฅ๐ง๐๐! ๐๐ฅ
Super VL NVFP4 recipe:
github.com/vcruz305/Nemotronโฆ
Bolt 24GB recipe:
github.com/vcruz305/Nemotronโฆ
๐จ NVIDIA NEMOTRON 3.5 SUPER VL & BOLT ARE HERE! ๐ข๐ฅ
I've been keeping a BIG secret for the past week...
For the first time, @nvidiaai gave me PRE-RELEASE ACCESS to their latest model weights, and I've spent the past week testing, benchmarking, and experimenting with Nemotron 3.5 Super VL on my very own DGX Spark at home!
And let me tell you... NVIDIA has been COOKING! ๐คฏ
๐ง MEET NEMOTRON 3.5 SUPER VL
We're talking about a 120B parameter multimodal MoE model with only 12B active parameters!
โ
Advanced reasoning, coding & tool calling
โ
Image, video & document understanding
โ
Up to 1M token context with supported configurations
โ
Hybrid Mamba-2 + Transformer architecture
โ
Native Multi-Token Prediction (MTP)
โ
NVFP4 weights running LOCALLY on my DGX Spark!
But here's where things get REALLY interesting...
NVIDIA told me this model could compete with, and even outperform, its MUCH larger 550B parameter sibling, Nemotron 3 Ultra.
Naturally, I had to put that claim to the test myself. ๐
๐งช MY SIXCAT RESULTS ARE IN!
120 challenging questions. Six categories. Same benchmark.
๐ฃ NEMOTRON 3 ULTRA 550B (55B ACTIVE)
๐ 82.50% | 99/120 PASSED
๐ข NEMOTRON 3.5 SUPER VL 120B (12B ACTIVE)
๐ 84.17% | 101/120 PASSED
SUPER VL TAKES THE LEAD! ๐ฅ
๐ CATEGORY BREAKDOWN (SUPER VL vs ULTRA)
๐ง Knowledge: 85% vs 80% โ
๐ข Math: 100% vs 100%
๐ฏ Truthfulness: 85% vs 85%
๐ Instruction Following: 50% vs 50%
๐ป Code: 100% vs 95% โ
๐ง Tool Use: 85% vs 85%
That's a 1.67 percentage-point lead for a model with roughly 4.6X FEWER total parameters!
And Super VL brings multimodal capabilities to the table too!
For transparency: Ultra was tested through OpenRouter with thinking enabled, while Super VL ran locally in NVFP4 using vLLM. Super also encountered five truncated instruction responses and six loop failures. These are real first-response results across different deployments, not proof of universal superiority.
But seeing the smaller model pull ahead on my independent evaluation is EXCITING!
๐ NOW LOOK AT THE DGX SPARK FRONTIER!
Check out the official NVIDIA-provided chart attached to this post!
According to the published local.ai measurements, Nemotron 3.5 Super achieves:
๐ง 80.0 Intelligence Index
โก 6.5 minutes per agentic task
๐ฅ๏ธ On a single 128GB DGX Spark!
These are published frontier measurements, separate from my SixCat results.
This is EXACTLY why I'm so passionate about local AI. We are reaching levels of intelligence and efficiency that would've required substantially more expensive hardware not long ago!
โก AND NVIDIA DIDN'T STOP THERE... MEET NEMOTRON 3.5 BOLT!
NVIDIA also introduced a new family of models optimized for LOCAL AGENTS!
๐น Nemotron 3.5 Bolt 74B-A9B
74B total parameters, just 9B active, optimized with native 2-bit quantization to fit within approximately 24GB!
Designed for local coding, research, tool use, and agentic workflows on RTX systems and DGX Spark.
๐น Nemotron 3.5 Bolt E4B
An even smaller 4GB-class model built for fast conversational and edge agents, arriving October 23!
And this is where my mind immediately went...
WHAT IF WE COULD RUN SUPER VL AS THE MASTER MODEL AND BOLT AS ITS SUB-AGENT... SIMULTANEOUSLY ON ONE DGX SPARK?! ๐
If you've been following my TWO MODELS. ONE SPARK. series, you probably know EXACTLY where I'm going with this. ๐
๐ A HUGE THANK YOU TO @nvidiaai!
This is my first official pre-release weights access, and I genuinely couldn't be more grateful.
Having NVIDIA trust me to test, optimize, benchmark, and explore these weights ahead of launch means a lot to me.
My mission has always been to make powerful AI models more accessible to the community, especially those without access to expensive datacenter GPUs.
And I've spent the past week working on something VERY SPECIAL with these weights...
๐งช Let's just say I managed to shrink something considerably while keeping some VERY impressive fidelity numbers.
โฐ 10 AM PACIFIC. NEXT ANNOUNCEMENT.
TWO MODELS. ONE SPARK. โก
๐ OFFICIAL HUGGING FACE WEIGHTS
๐ข Super VL BF16:
huggingface.co/nvidia/NVIDIAโฆ
๐ข Super VL NVFP4:
huggingface.co/nvidia/NVIDIAโฆ
โก Bolt 74B-A9B BF16 huggingface.co/nvidia/NVIDIAโฆ
๐ OFFICIAL NVIDIA BLOGS
Launch announcement:
blogs.nvidia.com/blog/nemotrโฆ
Technical deep dive:
developer.nvidia.com/blog/nvโฆ
The future of powerful, PRIVATE, locally hosted AI is getting VERY exciting.
And we're only getting started! ๐๐ฅ
๐ ๐ฆ๐ง๐๐ฃ ๐ฑ ๐ฃ๐ฅ๐๐ฉ๐๐๐ช: ๐๐๐ฌ-๐ญ๐๐ฅ๐ข ๐๐๐จ๐๐!
The weights dropped. I got to work.
GGUFs for the community. DAY ZERO. ๐ฅ
@StepFun_aiโs new 600B-class model is here, and Iโve published my GGUF conversions on @huggingface!
The mission stays the same: bring big models closer to the hardware we actually own.
๐ง ๐ ๐๐๐ ๐ฅ๐๐๐๐๐ฆ๐ ๐๐ข๐ฅ ๐๐ข๐๐๐ ๐๐
Step 5 Preview is StepFunโs flagship for agentic work: repository-level coding, extended tool-driven workflows and professional research.
StepFun specifies 600B total parameters with 27B active per token.
Now there are community GGUFs to start exploring it beyond the API.
๐ฆ ๐ง๐ช๐ข ๐ฃ๐๐๐๐ฆ ๐๐ฅ๐ ๐๐๐ฉ๐
โก IQ1_S: 111.32 GiB, approximately 120 GB.
An aggressive 1.599-bpw text pack targeting single-DGX-Spark experiments. Significant reasoning-quality loss is the tradeoff at this size.
๐ช Q4_K_M: approximately 361 GB.
A higher-bit alternative for larger-memory systems and multi-device experimentation.
Both packs have all 25 shards uploaded.
These are weight-file sizes, not total runtime memory requirements. Leave room for the KV cache and runtime overhead.
๐ ๏ธ ๐ง๐๐ ๐๐๐ง๐๐๐๐ฆ ๐ ๐๐ง๐ง๐๐ฅ
The repo includes importance-matrix calibration material and documented fixes for the modelโs rotary-position metadata.
The text packs contain roughly 598B parameters. Vision, MTP and sparse-attention components are preserved separately as companion GGUFs.
All 902 companion tensors were checked byte-for-byte against the source checkpoint: ZERO mismatches. Uploaded companion files were also verified by SHA-256.
Preserving the weights matters, even where runtime support still needs to catch up.
๐ฌ ๐๐๐ฌ-๐ญ๐๐ฅ๐ข ๐ฆ๐ง๐๐ง๐จ๐ฆ
This is an early text-inference release, not a claim of full feature parity.
The documented llama.cpp path does not yet execute the vision, MTP or sparse-attention companions. Full multimodal support and 1M-context GGUF operation are not being claimed here.
Compatibility notes and limitations are in the model card.
๐ ๐๐จ๐๐๐ง ๐๐ข๐ฅ ๐ง๐๐ ๐๐ข๐ ๐ ๐จ๐ก๐๐ง๐ฌ
Huge credit to @StepFun_ai for releasing the weights, the llama.cpp contributors, and @huggingface for making community distribution possible.
My part: getting the GGUF conversions into your hands on day zero.
Grab a pack, test it, and share your hardware, settings and results. Letโs turn a new model release into community progress. โก
๐ข๐ฝ๐ฒ๐ป ๐๐ฒ๐ถ๐ด๐ต๐๐ ๐ฎ๐ฟ๐ฒ ๐๐ต๐ฒ ๐๐๐ฎ๐ฟ๐๐ถ๐ป๐ด ๐น๐ถ๐ป๐ฒ. ๐๐ฒ๐โ๐ ๐ฏ๐๐ถ๐น๐ฑ.
๐ GGUFs:
huggingface.co/vcruz305/Stepโฆ
Introducing Step 5 Preview: Advancing the Pareto Frontier.
Step 5 Preview is our new flagship model for agentic work, delivering frontier-level performance across software engineering and professional knowledge work, with particular strength in finance.
- 600B total / 27B active MoE, with 1M context + Vision
- Substantially lower task cost at comparable intelligence
- Broad software engineering capabilities with sustained execution over long horizons
Try Step 5 Preview: platform.stepfun.ai
Model page: stepfun.com/step-5-preview
Open weights on Oct 15.
๐ ๐ง๐ช๐ข ๐ ๐ข๐๐๐๐ฆ ๐ข๐ก๐ ๐ฆ๐ฃ๐๐ฅ๐!
One main frontier level agent running Qwen3.8-Flash Next. Up to eight concurrent sub agents running MiniCPM-V 4.7 35B-A3B. A shared 1M-token worker KV pool.
All on ONE NVIDIA DGX Spark. ๐ฅ
Iโm launching a new recipe series built around a different question:
Not just โWhatโs the biggest model I can fit?โ
But โHow much useful work can this machine actually do?โ
Not two unrelated chat windows. Two models working together, with real delegation, tool use and measured results.
๐ง ๐ ๐๐๐ง ๐ง๐๐ ๐ง๐๐๐
Qwen3.8-Flash-Next EXL3 โข 3.05 bpw
The main agent: owns the conversation, delegates tasks and brings the results together.
MiniCPM-V 4.7 35B-A3B SAGE EXL3 โข 3.74 bpw
The worker model: serves the delegated subagents.
ExLlamaV3 + Hermes Agent. One GB10. 128 GB unified memory.
Both models stay loaded. No second Spark. No cloud model endpoint. No swapping models for each task.
๐งฎ ๐ข๐ก๐ ๐ ๐๐๐๐๐ข๐ก ๐ง๐ข๐๐๐ก๐ฆ ๐๐ข๐ฅ ๐ง๐๐ ๐ช๐ข๐ฅ๐๐๐ฅ๐ฆ
MiniCPM has a shared Q4 KV pool of 1,048,576 tokens, with the Hermes profile allowing:
8 concurrent workers ร 131,072-token context limits.
One loaded worker model, NOT eight copies. Separate conversation contexts sharing a cache budget, NOT a shared conversation or 1M tokens per worker.
Qwen keeps its own separate 262,144-token Q8 KV cache.
Additional tasks queue in Hermes. Full worker-pool saturation testing is still ahead.
โ
๐ฅ๐๐๐ ๐๐๐๐๐๐๐ง๐๐ข๐ก. ๐๐๐๐๐๐๐ ๐ฅ๐๐ฆ๐จ๐๐ง๐ฆ.
Qwen delegated file-reading and calculation tasks. Workers used tools, returned their answers and Qwen assembled the result.
4 tasks: 4/4 correct in ~92s.
8 tasks: 8/8 correct in ~123s.
12 tasks: 12/12 correct in ~218s.
16 tasks: 16/16 correct in ~321s.
Routing audit: 44 subagent sessions on MiniCPM, five parent sessions on Qwen. ZERO cross-routed sessions.
Both models passed streaming and non-streaming tool-calling checks.
โก ๐๐ข๐ง๐ ๐๐ข๐๐๐๐. ๐๐ข๐ง๐ ๐ช๐ข๐ฅ๐๐๐ก๐.
Other model loaded but idle:
Qwen: 88.6 tok/s code / 55.9 prose.
MiniCPM: ~69.8 tok/s.
Both actively generating code:
Qwen: 35.3 tok/s.
MiniCPM: 40.0 tok/s.
Those are concurrent measurements, not standalone numbers added together.
In the heavier eight-worker synthetic test with ~7.2K-token prompts and tool schemas, Qwen maintained 26.2 tok/s while MiniCPM delivered 25.8 tok/s aggregate, measured end-to-end.
๐ ๏ธ ๐๐ข๐ช ๐๐ง ๐๐๐ง๐ฆ
Qwenโs ~31 GB n-gram embedding table streams from NVMe, freeing RAM for MiniCPM and its worker cache. This is NOT cold-expert offloading.
More than 20 GB of available memory remained in the heaviest measured run.
128K retrieval checks passed on each model with the other loaded, plus simultaneous 64K checks on both. Cold 128K first-token latency was ~206s for Qwen and ~90s for MiniCPM.
๐ฆ ๐ง๐๐ ๐ฅ๐๐๐๐ฃ๐ ๐๐ฆ ๐๐๐ฉ๐
Setup, downloads, coordinated startup/shutdown, memory guards, a separate Hermes profile, tests and measured results.
๐ Credit: @Alibaba_Qwen @QwenDevs @OpenBMB @turboderp_ @NousResearch
My contributions: SAGE MiniCPM quantization, recipes, integration and measurements.
@NVIDIAAI ๐
Weโve spent a lot of time asking whether one model fits on a Spark.
๐๐ฒ๐โ๐ ๐ฏ๐๐ถ๐น๐ฑ ๐๐ต๐ฒ ๐๐ฒ๐ฎ๐บ ๐๐ต๐ฎ๐ ๐ฟ๐๐ป๐ ๐ผ๐ป ๐ถ๐. โก
github.com/vcruz305/TWOMODELโฆ
MiniCPM-V 4.7 35B-A3B EXL3 just hit 125 tok/s on ONE DGX Spark with REXL3, our stealth inference engine! ๐คฏ
3.74 bpw. Under 18 GB of weights. Built for 24 GB GPUs and up.
And the original model beats Qwen3.6-35B-A3B on some seriously impressive benchmarks.
๐ช๐๐ฌ ๐ ๐๐ก๐๐๐ฃ๐ -๐ฉ ๐ฐ.๐ณ?
35B total parameters, only ~3B active per token, with vision, OCR, document and video understanding.
OpenBMB's published original-model results vs Qwen3.6-35B-A3B:
โ OmniDocBench: 94.24 vs 80.17
โ OCRBench: 91.20 vs 86.00
โ IFBench: 47.67 vs 35.33
โ ฯยฒ-Bench: 84.65 vs 79.65
These are upstream model benchmarks, not scores rerun on my quant.
๐ ๐ฌ ๐ฆ๐๐๐ ๐๐ซ๐๐ฏ ๐ฅ๐๐๐๐๐ฆ๐
Instead of applying flat precision everywhere, SAGE allocates bits based on sensitivity.
17.99 GB of target weights
3.74 bpw
8-bit vision included
Measured against BF16-reference logits:
Held-out:
93.64% top-1 | KL 0.03148
Independent:
93.13% top-1 | KL 0.03169
20,480 evaluated token positions across both sets.
Top-1 measures how often the quant picks the SAME most-likely next token as BF16. KL measures differences across the entire probability distribution. Lower is better.
SixCat v0.7.0: 79.17 overall, including 100 Math, 90 Tools and 85 Code.
๐ข๐ก๐ ๐๐๐ซ ๐ฆ๐ฃ๐๐ฅ๐
ExLlamaV3 + TabbyAPI:
69.7 tok/s decode p50
1,024 tok/s prefill p50
REXL3, our stealth Rust inference engine:
125 tok/s ๐
The REXL3 result is a separate early measurement, not a controlled head-to-head with the published ExLlamaV3 benchmark. More engine details are coming!
๐ก๐ข๐ช ๐ช๐๐ง๐ ๐ ๐ฃ๐จ๐๐๐๐ ๐ฅ๐๐๐๐ฃ๐
I also released a serving recipe with:
โ Latest ExLlamaV3 and TabbyAPI forks, automatically checked on new launches
โ Native MiniCPM text and vision support
โ 24 GB GPU, vision and DGX Spark deployment profiles
โ Model integrity checks and reproducible benchmark tools
One particularly interesting use case is keeping MiniCPM as a compact vision/OCR companion alongside a larger model on a 128 GB Spark.
That's the goal, although simultaneous deployment still needs validation. Discrete 24 GB cards also need their own tests.
The full model doesn't have to occupy your entire machine to be useful.
Huge credit to @openbmb for MiniCPM-V and @turboderp for EXL3 and @mr_r0b0t for the dspark improvements to Exllamav3!
EXL3 weights:
huggingface.co/vcruz305/Miniโฆ
NEW serving recipe:
github.com/vcruz305/MiniCPM-โฆ
๐ Introducing MiniCPM-V 4.7, our new open-source MLLM series!
Advancing the PerformanceโEfficiency Pareto Frontier.
It brings strong multimodal capabilities to iOS and Android devices with extreme efficiency.
Two new models:
๐น MiniCPM-V 4.7 35B-A3B โ Bring SOTA performance to local devices with newly introduced LES (Lookahead Expert Scheduling) technique, a new milestone of on-device multimodal AI.
๐น MiniCPM-V 4.7 1B โ Lightweight, efficient multimodal AI. Easier to deploy.
โก What's new?
SOTA performance: Competitive results across 34 benchmarks spanning multimodal understanding, STEM reasoning, OCR and long-video comprehension.
Fast on-device inference: LES predicts and preloads expert weights to reduce inference stalls, boosting 5ร speedup on iPad Pro M4 (16GB) with byte-for-byte identical outputs. It enables MiniCPM-V 4.7 35B-A3B to achieve 17+ tokens/s on iPad Pro M4 (16GB) and 13+ tokens/s on iPhone 17 Pro Max, while costing only 3GB memory ๐คฏ
Efficient visual processing: 4ร and 16ร hybrid visual token compression. Even at 16ร compression, 35B-A3B scores 90.4 on OCRBench, 5.2 points ahead of Qwen3.6 35B-A3B.
Easier customization: We introduce Self-Replay Fine-Tuning, a simple way to customize new target capabilities at low cost while maintaining general performance.
Broad hardware support: Day-0 adaptations for Apple, Intel, AMD, Arm and Rockchip, with many more platforms supported through FlagOS!
Download, deploy, and build something we haven't imagined yet. ๐๐
๐ GitHub: github.com/OpenBMB/MiniCPM-V
๐ค Hugging Face: huggingface.co/collections/oโฆ
Another day and another amazing post by @yume_arasaki on the GLM-5.3-Flash cyber fine-tune called RED-SNOW-5.3-FLASH created by the awesome @Blackfrost_AI and quantized to EXL3 by yours truly! ๐
The craziest results are the 12 cybersecurity tasks, judge-scored, 21 of 22 points ๐คฏ:
CWE identification: 8 of 8. Crypto: 4 of 4. Web: 4 of 4. Attack-path: 2 of 2. Detection: 3 of 4. All from a ONE DGX SPARK quant of GLM-5.3-FLASH! ๐ฅ
One spark:
huggingface.co/vcruz305/RED-โฆ
Two sparks:
huggingface.co/vcruz305/RED-โฆ
You can run GLM-5.3-Flash abliterated on one DGX Spark. 321B parameters. One box. 262k context. I tested it.
The model is RED-SNOW-5.3-FLASH by @Blackfrost_AI, an abliterated build of the official GLM-5.3-Flash. The quant and the recipe that squeeze it into one Spark are by @ViC305, Cruz.
A model this size on one box is only interesting if it still works, so I spent 2 days finding out, so you do not have to.
Twelve judge-scored cybersecurity tasks. Long-context recall out to 240k. Agent speed across structured output, code, JSON, and prose.
I do not condone harmful use of these models. There are legitimate reasons to run unlocked weights, and security work is the main one.
Part 1 of 2.
THE RECIPE
2.49 bits per weight, SAGE EXL3. 15 shards, 97.4 GiB. That is how 321B fits in 128 GB with room left for context.
Served through tabbyAPI on Cruz's exllamav3 fork. 51.5 seconds to load. MTP and n-gram speculation on. 262k context.
Pin the fork at 7c1636f. The newer merged build read 17.1 tok/s on the same prompt against 22.9 on the pin. Same box, same weights, 25 percent slower for upgrading.
Uncensored GLM is a crowded shelf: this is a first-party abliteration on the official zai-org base, not a rebrand of someone else's.
The ablation is documented in the pack config, a refusal-direction subtraction at alpha 2.3 over 17,132 red-team examples.
THE SPEED
Single stream, one Spark:
Structured output: 43.2 tok/s. Code: 40.7. JSON: 32.1. Prose: 29.2. A 34k-token agent turn: 78.1.
Structured and code lead because the speculation has something to predict. Prose is the honest floor.
Depth is the cost. Decode falls from 11.3 tok/s at 8k to 0.7 at 240k. The window is real. Living at the far end of it is slow.
WHAT IT CAN DO
12 cybersecurity tasks, judge-scored, 21 of 22 points.
CWE identification: 8 of 8. Crypto: 4 of 4. Web: 4 of 4. Attack-path: 2 of 2. Detection: 3 of 4.
The one miss was not a knowledge gap. The model spent its whole token budget reasoning and never wrote a final answer. Hold that thought.
Needle in a haystack, three depths, out to 240k: 15 of 15.
At 2.49 bits, on one box, that is a working model. Abliteration and heavy quantization are both supposed to cost you something. On these tasks I could not find the bill.
FYI @ViC305 has a higher bpw version for two sparks. At 5+ bpw, this should land closer to FP8, which would mean two sparks can run this recipe close to lossless.
THE CATCH
GLM-5.3 removed thinking-off. Z.ai says it in the release notes: disabling thinking is no longer supported.
Your server will still accept enable_thinking false. It just ignores it.
My first needle run scored 0 of 15 at every depth. The model reasoned anyway, spent the 64-token answer budget inside its think block, and never answered. Same model, budget raised to 512: 15 of 15 to 240k.
That is the cyber miss too. Same failure, different task.
If you run GLM-5.3 locally with a small max_tokens, your scores are wrong and your agents are returning empty strings. Budget for thinking. Always.
Credit to the pack: its template adds a thinking gate stock GLM lacks. Not enough on its own, but an honest attempt to restore a switch the base model took away.
THE PERSONA PROMPT
The pack also ships a persona prompt baked into its chat template. Every turn, it tells the model it is an offensive hacker on authorized work and must never refuse. It costs 168 tokens per turn, and it hides in two files, so swapping one does not remove it.
So I tested it. Same weights, same server, same 60 prompts. One arm on the stock GLM template, one on the shipped template. Authorized security work, harmful controls, benign canaries.
On this panel, compliance did not move. Every prompt complied in both arms. The abliteration lives in the weights, and on these 60 prompts the persona added nothing to it.
One difference did show up. Empty answers: 3 on stock, 0 on shipped. A small sample, but the persona arm was the cleaner one. Whether it matters on other workloads, I have not tested.
SCOPE
One 2.49bpw quant, one Spark, one week. 60 prompts per arm, GLM judge at temperature 0. Harmful examples deliberately not listed, but ran for real.
Part 2 is the complete speed run. The dual-Spark run lands later this week.
Source, findings and receipts in reply ๐
53 tok/s! ๐Phenomenal work by @justinn_builds getting the GLM-5.3-Flash cyber fine-tuned ablit RED-SNOW-5.3-FLASH EXL3 collab with @Blackfrost_AI to 53tps across two DGX Sparks!! Bravo my brother, just another example of the community doing its thing and working its magic with my EXL3 quants!! Grateful for all the time invested ๐
Recipe:
github.com/justincasey/RED-Sโฆ
Quant:
huggingface.co/vcruz305/RED-โฆ
My first recipe serving Red Snow for 2 Sparks.
โข Code/JSON: ~47โ53 tok/s
โข Prose: ~30โ37 tok/s
โข TensorFold TP=2 + DFlash2 drafting, EXL3 4.91bpw
Built with work from @ViC305 @Blackfrost_AI @ashxhart and @MiaAI_lab
github.com/justincasey/RED-Sโฆ
This is why I LOVE this community, I didnโt even ask for this and he took the time to work through the switchless method and BOOM my GLM-5.3 full EXL3 tp4 quant running at 37tps! Insane work and very much appreciated! Iโll be updating the readme with this as an option for my switchless folk!
The README of @ViC305's full GLM-5.3 recipe asks for a switch to connect four DGX Sparks.
I ran it without one: four cables in a ring. Same 6 test prompts from his repo:
Switch + his RoCE reduce: 41.4 tok/s
Switch + NCCL: 37.1 tok/s
My ring (NCCL): 36.4 tok/s
No switch costs 12% against his best setup, and 2% against NCCL on the switch.
Not identical: his numbers are in-process at 32K context, mine go through the server at 131K. 3 of 6 prompts gave other tokens than his reference (from token 24, 42 and 119). I have not measured why.
How to cable it is in the reply.
Letโs gooooo finally some good learning content from one of the main leaders in the abliteration industry! @Blackfrost_AI is an official security firm with the magic sauce! Learn how to ablit a dense model quickly and the RIGHT way without butchering the models intelligence ๐ซก
Side note, he sells official commercially licensed full abliterated (what he terms DERISKED) models for enterprise use! Give him a follow and some love for taking his time to create a course to help others!
โ๏ธBlackfrost Learning is live.
FULL MODEL REFUSAL REMOVAL COURSE
DOWNLOADS INCLUDED
Our first course, DWM Foundations, turns a real Qwen 9B model-editing case study into a free, self-paced lesson on method, measurement, and verification. No account required.
blackfrostai.com/learn/dwm-fโฆ
I need to make a serious correction! My first GitHub sponsor was @TrickRiggin!! Iโm extremely grateful for people like him who donโt even ask for any type of recognition and even when I mistakened the post he was super cool about it! God bless you for putting your own money into my work! ๐ซก
And then to make it right @SixZzshOtRipZz just sponsored me for $75 a month!! Wow man I canโt believe it!! God is so good! May God bless you as well for putting your hard earned money into my work!! I will be hooking yall up even more often!! Thank you all and thank you Jesus! ๐ฉ๐
I just got my FIRST GITHUB SPONSOR!! ๐คฏ
@SixZzshOtRipZz, thank you for putting your own hard-earned money behind my work. Seriously, this means so much to me.
I started sharing quants, tools and fixes because I wanted more people to run these models on the hardware they already have. I genuinely never imagined someone would decide to sponsor me for it.
$60/year, the equivalent of $5/month. Knowing someone believes in what Iโm building enough to support it is a milestone I wonโt forget.
And small contributions add up. Just 10 more people at $5/month would add $50/month toward rented compute for bigger quants, more testing and more public releases.
๐ ๐ข๐ฅ๐ ๐ช๐๐ฌ๐ฆ ๐ง๐ข ๐ฆ๐จ๐ฃ๐ฃ๐ข๐ฅ๐ง
Iโve also created three Ko-fi tiers:
$5/month โข Local AI Supporter
Help fund public model quants, open-source tools and benchmarks. Includes project updates and behind-the-scenes notes.
$15/month โข AI Lab Backer
All Supporter benefits, plus optional supporter credit. Help fund SAGE-EXL3, vllm-exl3, SixCat and ongoing experiments.
$50/month โข Frontier AI Champion
All Backer benefits, plus one custom model quantization AND a matching serving recipe each month, tailored to your hardware. Weโll agree on the model and compute requirements first.
Have a model youโve been wanting to run locally? Thatโs exactly the kind of work I love doing.
Public shout-outs are optional at every tier. Supporting quietly means just as much to me.
๐ ๐ฌ ๐ฃ๐จ๐๐๐๐ ๐ช๐ข๐ฅ๐ ๐ฆ๐ง๐๐ฌ๐ฆ ๐ฃ๐จ๐๐๐๐
My public quants, tools and recipes arenโt going behind a paywall. This is optional support for the work behind them.
To everyone who sponsors, tests a build, submits a PR, lends hardware or shares a release: thank you. Youโre helping me take this work further than I could alone. ๐
GitHub Sponsors:
github.com/sponsors/vcruz305โฆ
Ko-fi memberships:
ko-fi.com/victorangelcruz/tiโฆ

































