on

Can the NVIDIA H200 NVL run Flow Judge v0.1?

60Good quality (B) · 60 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.

Yes, it runs well

Runs well. At Q4_K_M it needs about 10.8 GB of 141 GB usable and makes one decision in about 147 ms.

Best quant
Q4_K_M
Time per decision
147 ms
Decisions per second
6.8/s
Input assumed
1,024 tokens
Returns
Written feedback, then a score

Best app to run it on the NVIDIA H200 NVL

On Linux

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
vllm serve flowaicom/Flow-Judge-v0.1
  • LM Studio Point-and-click: search, download and chat in one window.
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.

On Windows

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

Recommended for the NVIDIA H200 NVL: Q4_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 Q4_K_M file (opens in a new tab)

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

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

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 60Good quality (B) · 60 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.
How capable the model itself is at Q4_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: S 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs well
How well it runs on the NVIDIA H200 NVL: 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.27.4 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.25.0 / 25
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.12.4 / 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 score73.8 / 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 NVIDIA H200 NVL

Quant Memory needed Available Time per decision Runs Quality Download
Q4_K_M 10.8 GB 141 GB 147 ms Runs well 60Good quality (B) · 60 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. GGUF (opens in a new tab)
Q5_K_M 11.2 GB 141 GB 167 ms Runs well 62Good quality (B) · 62 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 11.6 GB 141 GB 189 ms Runs well 63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 12.5 GB 141 GB 240 ms Runs well 64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 16.1 GB 141 GB 464 ms Slow 64Good quality (B) · 64 of 100: how capable the model is at F16, whatever it runs on. Match score 69/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

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.