Qwen3Guard Gen 0.6B on AMD Radeon RX 7900 XTX
Can the AMD Radeon RX 7900 XTX run Qwen3Guard Gen 0.6B?
Yes, it runs great
Runs great. At F16 it needs about 3.5 GB of 24.0 GB usable and makes one decision in about 28 ms.
- Best quant
F16- Time per decision
- 28 ms
- Decisions per second
- 36/s
- Input assumed
- 512 tokens
- Returns
- Fixed labels
Best app to run it on the AMD Radeon RX 7900 XTX
On Windows
- AMD’s own app: llama.cpp tuned for Radeon on Vulkan and ROCm.
lemonade pull mradermacher/Qwen3Guard-Gen-0.6B-GGUF:F16Download Qwen3Guard Gen 0.6B
Recommended for the AMD Radeon RX 7900 XTX: F16. 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 F16 file (opens in a new tab)
huggingface.co/mradermacher/Qwen3Guard-Gen-0.6B-GGUF (opens in a new tab)
ollama run hf.co/mradermacher/Qwen3Guard-Gen-0.6B-GGUF:F16Original weights · Hugging Face
Full-precision files from Alibaba, for fine-tuning, vLLM, Transformers.
huggingface.co/Qwen/Qwen3Guard-Gen-0.6B (opens in a new tab)
How it’s rated
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.
| Precision | 33.3 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 15.0 / 15 | |
| Clarity | 12.0 / 15 | |
| Match score | 85.3 / 100 |
Every quantization on the AMD Radeon RX 7900 XTX
| Quant | Memory needed | Available | Time per decision | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q4_K_M | 2.5 GB | 24.0 GB | 13 ms | Runs great | 70Great quality (A) · 70 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q5_K_M | 2.6 GB | 24.0 GB | 14 ms | Runs great | 71Great quality (A) · 71 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q6_K | 2.6 GB | 24.0 GB | 15 ms | Runs great | 73Great quality (A) · 73 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q8_0 | 2.8 GB | 24.0 GB | 18 ms | Runs great | 74Great quality (A) · 74 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
F16 | 3.5 GB | 24.0 GB | 28 ms | Runs great | 74Great quality (A) · 74 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) Original weights (opens in a new tab) |
Times are for one request with a 512-token input and about 6 tokens written. Batching servers process many requests at once.
Other hardware that runs it
-
74Great quality (A) · 74 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 9070 XT
-
74Great quality (A) · 74 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
AMD Ryzen AI Max+ 395 (128 GB)
-
74Great quality (A) · 74 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
Apple M1 Max (64 GB)
-
74Great quality (A) · 74 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
Apple M2 Ultra (192 GB)
-
74Great quality (A) · 74 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
Apple M3 Ultra (256 GB)
-
74Great quality (A) · 74 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
Apple M3 Ultra (512 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.