Flow Judge v0.1 on Intel Xeon Silver (4100 to 4300 series) NAS (512 GB)

Can the Intel Xeon Silver (4100 to 4300 series) NAS (512 GB) run Flow Judge v0.1?

Barely: it runs very slowly

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

Best quant: Q8_0
Time per decision: 27.6 s
Decisions per second: 0.0/s
Input assumed: 1,024 tokens
Returns: Written feedback, then a score

Best app to run it on the Intel Xeon Silver (4100 to 4300 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 flowaicom/Flow-Judge-v0.1-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 Flow Judge v0.1

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

huggingface.co/flowaicom/Flow-Judge-v0.1-GGUF (opens in a new tab)

ollama run hf.co/flowaicom/Flow-Judge-v0.1-GGUF

Original weights · Hugging Face

Full-precision files from Flow AI, for fine-tuning, vLLM, Transformers.

huggingface.co/flowaicom/Flow-Judge-v0.1 (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 64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 63/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 Silver (4100 to 4300 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.	28.8 / 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.9 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.	9.0 / 15
Match score	63.7 / 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 Silver (4100 to 4300 series) NAS (512 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q4_K_M`	41.4 GB	471 GB	19.5 s	Very slow	60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	41.8 GB	471 GB	21.3 s	Very slow	62Good quality (B) · 62 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q6_K`	42.2 GB	471 GB	23.2 s	Very slow	63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q8_0`	43.1 GB	471 GB	27.6 s	Very slow	64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`F16`	46.7 GB	471 GB	46.8 s	Very slow	64Good quality (B) · 64 of 100: how capable the model is at F16, whatever it runs on. Match score 63/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 1,024-token input and about 150 tokens written. Batching servers process many requests at once.

Other hardware that runs it

60Good quality (B) · 60 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. NVIDIA RTX PRO 6000 Blackwell Q4_K_M · 308 ms · Runs well
60Good quality (B) · 60 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. NVIDIA GeForce RTX 5090 Q4_K_M · 316 ms · Runs well
60Good quality (B) · 60 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 B200 Q4_K_M · 96 ms · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. AMD Instinct MI350X Q4_K_M · 118 ms · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. AMD Instinct MI325X Q4_K_M · 133 ms · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GB300 Grace Blackwell Ultra Desktop Superchip Q4_K_M · 138 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.