Hunyuan A13B (80B-A13B) on AMD Radeon PRO W7800 48GB
Can the AMD Radeon PRO W7800 48GB run Hunyuan A13B (80B-A13B)?
Yes, with little memory to spare
Tight fit. At Q3_K_M it needs about 43.5 GB of 48.0 GB usable, with an estimated speed of 45.4 tok/s.
- Best quant
Q3_K_M- Generation speed
- 45.4 tok/s
- Prompt processing
- 4,311 tok/s
- First token (1K prompt)
- 0.3 s
- Largest safe context
- 32K
Download Hunyuan A13B (80B-A13B)
Quantized files · GGUF
Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.
huggingface.co/tencent/Hunyuan-A13B-Instruct-GGUF (opens in a new tab)
ollama run hf.co/tencent/Hunyuan-A13B-Instruct-GGUFOriginal weights · Hugging Face
Full-precision files from Tencent, for fine-tuning, vLLM, Transformers.
huggingface.co/tencent/Hunyuan-A13B-Instruct (opens in a new tab)
Official repo · GitHub
Reference code, inference scripts and docs from Tencent. The weights themselves download from Hugging Face.
github.com/Tencent-Hunyuan/Hunyuan-A13B (opens in a new tab)
git clone https://github.com/Tencent-Hunyuan/Hunyuan-A13BHow the A grade is scored
Every result gets up to 100 points from four parts. The points decide the letter grade.
| Model quality | 28.0 / 45 | |
|---|---|---|
| Memory fit | 24.0 / 25 | |
| Speed | 15.0 / 15 | |
| Memory use | 15.0 / 15 | |
| Total | 82.0 / 100 | 81 ptsGreat (A) · 81 of 100 points: Model quality 28.0/45, Memory fit 24.0/25, Speed 15.0/15, Memory use 15.0/15 |
Every quantization on the AMD Radeon PRO W7800 48GB
| Quant | Memory needed | Available | Speed | Fit | Grade · points | Download |
|---|---|---|---|---|---|---|
Q2_K | 36.2 GB | 48.0 GB | 57.7 tok/s | Runs well | 78 ptsGreat (A) · 78 of 100 points: Model quality 23.3/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 | GGUF files (opens in a new tab) |
Q3_K_M | 43.5 GB | 48.0 GB | 45.4 tok/s | Tight fit | 81 ptsGreat (A) · 81 of 100 points: Model quality 28.0/45, Memory fit 24.0/25, Speed 15.0/15, Memory use 15.0/15 | GGUF files (opens in a new tab) |
Q4_K_M | 53.1 GB | 48.0 GB | 17.1 tok/s | Runs with offload | 66 ptsGood (B) · 66 of 100 points: Model quality 31.6/45, Memory fit 10.0/25, Speed 9.8/15, Memory use 15.0/15 | GGUF (opens in a new tab) |
Q5_K_M | 61.2 GB | 48.0 GB | 8.7 tok/s | Runs with offload | 64 ptsGood (B) · 64 of 100 points: Model quality 32.3/45, Memory fit 10.0/25, Speed 7.0/15, Memory use 15.0/15 | GGUF files (opens in a new tab) |
Q6_K | 70.0 GB | 48.0 GB | — | Won't run | 9 ptsWon't run (F) · 9 of 100 points: Model quality 9.9/45, Memory fit 0.0/25, Speed 0.0/15, Memory use 0.0/15 | GGUF files (opens in a new tab) |
Q8_0 | 89.3 GB | 48.0 GB | — | Won't run | 9 ptsWon't run (F) · 9 of 100 points: Model quality 10.0/45, Memory fit 0.0/25, Speed 0.0/15, Memory use 0.0/15 | GGUF · part 1 of 2 (opens in a new tab) |
F16 | 165 GB | 48.0 GB | — | Won't run | 9 ptsWon't run (F) · 9 of 100 points: Model quality 10.0/45, Memory fit 0.0/25, Speed 0.0/15, Memory use 0.0/15 | 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
- 87 ptsExcellent (S) · 87 of 100 points: Model quality 33.0/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 NVIDIA RTX PRO 6000 Blackwell
- 81 ptsGreat (A) · 81 of 100 points: Model quality 31.6/45, Memory fit 25.0/25, Speed 11.2/15, Memory use 14.0/15 Apple M4 Max (128 GB)
- 80 ptsGreat (A) · 80 of 100 points: Model quality 31.6/45, Memory fit 25.0/25, Speed 13.5/15, Memory use 10.0/15 Apple M2 Ultra (192 GB)
- 79 ptsGreat (A) · 79 of 100 points: Model quality 28.0/45, Memory fit 24.0/25, Speed 12.7/15, Memory use 15.0/15 Apple M4 Max (64 GB)
- 79 ptsGreat (A) · 79 of 100 points: Model quality 33.0/45, Memory fit 25.0/25, Speed 6.4/15, Memory use 15.0/15 AMD Ryzen AI Max+ 395 (128 GB)
- 78 ptsGreat (A) · 78 of 100 points: Model quality 31.6/45, Memory fit 25.0/25, Speed 13.7/15, Memory use 7.9/15 Apple M3 Ultra (256 GB)
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.