DynaGuard 1.7B on AMD Radeon RX 7600 XT
Can the AMD Radeon RX 7600 XT run DynaGuard 1.7B?
Yes, but slowly
Slow. At Q5_K_M it needs about 3.1 GB of 16.0 GB usable and makes one decision in about 1.3 s.
- Best quant
Q5_K_M- Time per decision
- 1.3 s
- Decisions per second
- 0.8/s
- Input assumed
- 512 tokens
- Returns
- Reasoned verdict
Best app to run it on the AMD Radeon RX 7600 XT
On Windows
- AMD’s own app: llama.cpp tuned for Radeon on Vulkan and ROCm.
lemonade pull mradermacher/DynaGuard-1.7B-GGUF:Q5_K_MDownload DynaGuard 1.7B
Recommended for the AMD Radeon RX 7600 XT: Q5_K_M. 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 Q5_K_M file (opens in a new tab)
huggingface.co/mradermacher/DynaGuard-1.7B-GGUF (opens in a new tab)
ollama run hf.co/mradermacher/DynaGuard-1.7B-GGUF:Q5_K_MOriginal weights · Hugging Face
Full-precision files from University of Maryland, for fine-tuning, vLLM, Transformers.
huggingface.co/tomg-group-umd/DynaGuard-1.7B (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 | 30.6 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 4.1 / 15 | |
| Clarity | 10.0 / 15 | |
| Match score | 69.7 / 100 |
Every quantization on the AMD Radeon RX 7600 XT
| Quant | Memory needed | Available | Speed | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q4_K_M | 2.9 GB | 16.0 GB | 1.1 s | Slow | 66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q5_K_M | 3.1 GB | 16.0 GB | 1.3 s | Slow | 67Good quality (B) · 67 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q6_K | 3.3 GB | 16.0 GB | 1.6 s | Very slow | 69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q8_0 | 3.8 GB | 16.0 GB | 2.1 s | Very slow | 70Great quality (A) · 70 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
F16 | 5.7 GB | 16.0 GB | 4.6 s | Very slow | 70Great quality (A) · 70 of 100: how capable the model is at F16, whatever it runs on. Match score 68/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 160 tokens written. Batching servers process many requests at once.
Other hardware that runs it
-
66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5090
-
66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4090
-
66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5080
-
66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 3090
-
66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5070 Ti
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.