on

Can the AMD EPYC 7002 / 7003 series NAS (256 GB) run MiniMax M3.1 Flash (428B-A23B)?

81Great quality (A) · 81 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.

Yes, but slowly (tight fit)

Slow (tight fit). At Q3_K_M it needs about 230 GB of 230 GB usable, with an estimated speed of 7.7 tok/s.

Best quant
Q3_K_M
Generation speed
7.7 tok/s
Prompt processing
17.4 tok/s
First token (1K prompt)
58.9 s
Largest safe context
9K

Best app to run it on the AMD EPYC 7002 / 7003 series NAS (256 GB)

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Usually the first to support new model architectures.
llama-server -hf unsloth/MiniMax-M3.1-Flash-GGUF:UD-Q3_K_XL

Want an agent? MiniMax M3.1 Flash (428B-A23B) supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, which apps run in a container on a NAS without a graphics card (models run on its processor), and whether the model fits fully in the memory models can use. Details.

Download MiniMax M3.1 Flash (428B-A23B)

Recommended for the AMD EPYC 7002 / 7003 series NAS (256 GB): Q3_K_M. Every other quantization has its own download link in the table below.

Ollama

Ollama offers this only as a cloud model (it runs on Ollama’s servers, not your machine). To run it locally, use the GGUF files below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q3_K_M (UD-Q3_K_XL) files (opens in a new tab)

huggingface.co/unsloth/MiniMax-M3.1-Flash-GGUF (opens in a new tab)

ollama run hf.co/unsloth/MiniMax-M3.1-Flash-GGUF

Original weights · Hugging Face

Full-precision files from MiniMax, for fine-tuning, vLLM, Transformers.

huggingface.co/MiniMaxAI/MiniMax-M3.1-Flash (opens in a new tab)

No sign-in needed.

How it’s rated

Quality 81Great quality (A) · 81 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q3_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Slowtight fit
How well it runs on the AMD EPYC 7002 / 7003 series NAS (256 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.36.7 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); fewer when it goes past that limit.24.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.6.6 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score82.2 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the AMD EPYC 7002 / 7003 series NAS (256 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 192 GB 230 GB 9.7 tok/s Slow 67Good quality (B) · 67 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (UD-Q2_K_XL) · folder (opens in a new tab)
Q3_K_M 230 GB 230 GB 7.7 tok/s Slowtight fit 81Great quality (A) · 81 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. GGUF (UD-Q3_K_XL) · folder (opens in a new tab)
Q4_K_M 282 GB 230 GB — Won't run 92Excellent quality (A+) · 92 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking. GGUF (UD-Q4_K_XL) · folder (opens in a new tab)
Q5_K_M 325 GB 230 GB — Won't run 94Excellent quality (A+) · 94 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 372 GB 230 GB — Won't run 96Excellent quality (A+) · 96 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 475 GB 230 GB — Won't run 97Excellent quality (A+) · 97 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 13/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 878 GB 230 GB — Won't run 97Excellent quality (A+) · 97 of 100: how capable the model is at F16, whatever it runs on. Match score 13/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?