Any idea why bartowski claims DeepSeek-V4-Flash is MXFP4?
Summary
A user questions why bartowski claims DeepSeek-V4-Flash is in MXFP4 format when the original model page lists BF16, F32, and other tensor types, not MXFP4.
Similar Articles
DeepSeek-V4-Flash (MXFP4): compute buffer scales ~3x just from KV cache quant type (f16 vs q8_0) — anyone else seeing this? Llama.cpp
A user reports that changing the KV cache quant type from f16 to q8_0 in DeepSeek-V4-Flash (MXFP4) causes the compute buffer to scale roughly 3x, asking if others have observed this behavior, specifically using llama.cpp.
@zcbenz: nvfp4 vs mxfp4 is not just different choices of block size and scale format, nvfp4 uses an additional tensor-wise scale…
A technical comparison between nvfp4 and mxfp4 formats, highlighting that nvfp4 uses an additional tensor-wise scale factor to overcome fp4's range limit, allowing more precision in block-wise scale factors.
Bringing Up DeepSeek-V4-Flash on AMD MI300X
This blog post details the author's efforts to get DeepSeek-V4-Flash running on AMD MI300X GPUs, highlighting software compatibility issues with the FP8 dialect and providing a worklog of the process.
Is DeepSeek v4 (Flash) really extremely cheap to run? If yes, how?
The user asks why DeepSeek v4 Flash (284B parameters) is so cheap to run compared to smaller models like Qwen 27B, questioning if it's due to pricing dumping or architectural differences. The answer likely involves its MoE architecture and efficient inference techniques.
How good is DeepSeek-V4 Flash, actually?
An evaluation of the performance and capabilities of DeepSeek-V4 Flash, assessing its real-world effectiveness.