Flow Judge v0.1 on Apple M5 Ultra (512 GB)

Can the Apple M5 Ultra (512 GB) run Flow Judge v0.1?

Yes, but slowly

Slow. At Q6_K it needs about 35.3 GB of 384 GB usable and makes one decision in about 822 ms.

Best quant: Q6_K
Time per decision: 822 ms
Decisions per second: 1.2/s
Input assumed: 1,024 tokens
Returns: Written feedback, then a score

Best app to run it on the Apple M5 Ultra (512 GB)

On macOS

LM Studio

Desktop app · runs on llama.cpp, MLX

Point-and-click: search, download and chat in one window.

Open Flow Judge v0.1 in LM Studio

llama.cpp Usually the first to support new model architectures.
Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). 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 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q6_K, 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 Slow: How well it runs on the Apple M5 Ultra (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.5 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; 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.	5.2 / 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	67.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 Apple M5 Ultra (512 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q4_K_M`	34.5 GB	384 GB	623 ms	Slow	60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	34.8 GB	384 GB	718 ms	Slow	62Good quality (B) · 62 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q6_K`	35.3 GB	384 GB	822 ms	Slow	63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q8_0`	36.2 GB	384 GB	1.1 s	Slow	64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`F16`	39.8 GB	384 GB	2.1 s	Very slow	64Good quality (B) · 64 of 100: how capable the model is at F16, whatever it runs on. Match score 66/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

Quick answers

How much memory does Flow Judge v0.1 need on the M5 Ultra 512GB?

At Q6_K it needs about 35.3 GB. The M5 Ultra 512GB has 384 GB usable.

How fast is Flow Judge v0.1 on the M5 Ultra 512GB?

It makes one decision in about 822 ms at Q6_K, an estimate from the hardware and the size of the model.

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.