DynaGuard 8B on Intel Xeon W-2100 series NAS (512 GB)

Can the Intel Xeon W-2100 series NAS (512 GB) run DynaGuard 8B?

Barely: it runs very slowly

Very slow. At Q8_0 it needs about 47.3 GB of 471 GB usable and makes one decision in about 51.0 s.

Best quant: Q8_0
Time per decision: 51.0 s
Decisions per second: 0.0/s
Input assumed: 512 tokens
Returns: Reasoned verdict

Best app to run it on the Intel Xeon W-2100 series NAS (512 GB)

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

Usually the first to support new model architectures.

llama-server -hf mradermacher/DynaGuard-8B-GGUF:Q8_0

Ollama Runs the Hugging Face GGUF with ollama run hf.co/…
LocalAI One OpenAI-compatible server for GGUF guard models and rerankers together.

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 DynaGuard 8B

Recommended for the Intel Xeon W-2100 series NAS (512 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/mradermacher/DynaGuard-8B-GGUF (opens in a new tab)

ollama run hf.co/mradermacher/DynaGuard-8B-GGUF:Q8_0

Original weights · Hugging Face

Full-precision files from University of Maryland, for fine-tuning, vLLM, Transformers.

huggingface.co/tomg-group-umd/DynaGuard-8B (opens in a new tab)

No sign-in needed.

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 79Great quality (A) · 79 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q8_0, 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 Very slow: How well it runs on the Intel Xeon W-2100 series NAS (512 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.

PrecisionEditorial precision tier from the model’s published benchmarks, scaled by the quantization or precision used.	35.6 / 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.	25.0 / 25
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.	0.7 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.	10.0 / 15
Match score	71.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 Intel Xeon W-2100 series NAS (512 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q4_K_M`	43.6 GB	471 GB	31.7 s	Very slow	75Great quality (A) · 75 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`	44.4 GB	471 GB	35.9 s	Very slow	76Great quality (A) · 76 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	45.3 GB	471 GB	40.5 s	Very slow	78Great quality (A) · 78 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	47.3 GB	471 GB	51.0 s	Very slow	79Great quality (A) · 79 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	55.0 GB	471 GB	97.0 s	Very slow	79Great quality (A) · 79 of 100: how capable the model is at F16, whatever it runs on. Match score 71/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

75Great quality (A) · 75 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA B200 Q4_K_M · 174 ms · Runs well
78Great quality (A) · 78 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. AMD Instinct MI350X Q6_K · 277 ms · Runs well
78Great quality (A) · 78 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GB300 Grace Blackwell Ultra Desktop Superchip Q6_K · 293 ms · Runs well
78Great quality (A) · 78 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. AMD Instinct MI325X Q6_K · 343 ms · Runs well
78Great quality (A) · 78 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H200 141GB SXM Q6_K · 368 ms · Runs well
78Great quality (A) · 78 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H200 NVL Q6_K · 373 ms · Runs well

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.