Hunyuan 1.8B Instruct on Apple M2 Pro (32 GB)
Can the Apple M2 Pro (32 GB) run Hunyuan 1.8B Instruct?
Yes, it runs well
Runs well. At Q8_0 it needs about 4.7 GB of 21.4 GB usable, with an estimated speed of 60.1 tok/s.
- Best quant
Q8_0- Generation speed
- 60.1 tok/s
- Prompt processing
- 2,355 tok/s
- First token (1K prompt)
- 0.4 s
- Largest safe context
- 256K
Download Hunyuan 1.8B Instruct
Recommended for the Apple M2 Pro (32 GB): Q8_0. Every other quantization has its own download link in the table below.
Quantized files · GGUF
Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.
Download the Q8_0 file (opens in a new tab)
huggingface.co/bartowski/tencent_Hunyuan-1.8B-Instruct-GGUF (opens in a new tab)
ollama run hf.co/bartowski/tencent_Hunyuan-1.8B-Instruct-GGUF:Q8_0Original weights · Hugging Face
Full-precision files from Tencent, for fine-tuning, vLLM, Transformers.
huggingface.co/tencent/Hunyuan-1.8B-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-7B (opens in a new tab)
git clone https://github.com/Tencent-Hunyuan/Hunyuan-7BHow the C grade is scored
Every result gets up to 100 points from four parts. The points decide the letter grade.
| Model quality | 9.9 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 15.0 / 15 | |
| Memory use | 5.1 / 15 | |
| Total | 55.0 / 100 | 55 ptsUsable (C) · 55 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 5.1/15 |
Every quantization on the Apple M2 Pro (32 GB)
| Quant | Memory needed | Available | Speed | Fit | Grade · points | Download |
|---|---|---|---|---|---|---|
Q2_K | 3.6 GB | 21.4 GB | 194 tok/s | Runs well | 50 ptsUsable (C) · 50 of 100 points: Model quality 6.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 3.8/15 | GGUF (opens in a new tab) |
Q3_K_M | 3.7 GB | 21.4 GB | 153 tok/s | Runs well | 52 ptsUsable (C) · 52 of 100 points: Model quality 8.3/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 4.0/15 | GGUF (opens in a new tab) |
Q4_K_M | 3.9 GB | 21.4 GB | 118 tok/s | Runs well | 53 ptsUsable (C) · 53 of 100 points: Model quality 9.4/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 4.2/15 | GGUF (opens in a new tab) |
Q5_K_M | 4.1 GB | 21.4 GB | 97.6 tok/s | Runs well | 54 ptsUsable (C) · 54 of 100 points: Model quality 9.6/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 4.4/15 | GGUF (opens in a new tab) |
Q6_K | 4.3 GB | 21.4 GB | 81.9 tok/s | Runs well | 54 ptsUsable (C) · 54 of 100 points: Model quality 9.8/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 4.6/15 | GGUF (opens in a new tab) |
Q8_0 | 4.7 GB | 21.4 GB | 60.1 tok/s | Runs well | 55 ptsUsable (C) · 55 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 5.1/15 | GGUF (opens in a new tab) |
F16 | 6.4 GB | 21.4 GB | 27.7 tok/s | Runs well | 54 ptsUsable (C) · 54 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 12.5/15, Memory use 6.9/15 | GGUF (opens in a new tab) 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
- 64 ptsGood (B) · 64 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 14.8/15 NVIDIA GeForce RTX 4060
- 60 ptsGood (B) · 60 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 10.2/15 Intel Arc B580
- 60 ptsGood (B) · 60 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 10.2/15 NVIDIA GeForce RTX 3060 12GB
- 60 ptsGood (B) · 60 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 10.2/15 NVIDIA GeForce RTX 4070 SUPER
- 57 ptsUsable (C) · 57 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 8.0/15 AMD Radeon RX 9070 XT
- 57 ptsUsable (C) · 57 of 100 points: Model quality 9.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 8.0/15 NVIDIA GeForce RTX 4060 Ti 16GB
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.